Hey @U0482NW9KL1 - yes, but the other way around, well-distributed UUIDs are the preferred ID type in v2. Our primary covering index is hash-oriented, so we can narrow searches-by-id down faster this way.

ahhhh thats interesting, that's convenient actually!

short answer is yes - it'll get duplicated. but also yes, the columnar compression should (eventually) be able to mitigate this, particularly as we compact our logs to be sorted first by eid, so different versions of the same entity will gravitate together in the primary index. that said, I'd also recommend that, if you know you're likely to have these kinds of update patterns, that you take advantage of the new tables by, where possible, splitting documents into faster and slower changing attributes. those documents can still have the same :xt/id values - these are now only required to be unique within a table.

Thanks, that was my intuition about it but I wanted to double-check. We have some member profile data that changes "a lot" and some that is much longer-lived, so that'll be something for us to consider if we move any of this stuff to XTDBv2 at some point.

How can multiple documents have the same :xt/id? I thought it must be unique like a primary key for each document. But reading above comments, I should be wrong. Can someone let me know where I can find the relevant part of the official documentation?

@U022N1DU7GQ in XT 1, that's correct - :xt/id is a primary key. in XT 2, we have tables - essentially different bags of documents - and it'll be that :xt/id only has to be unique within a table (same as a relational database)

Wow, I see. Excited to see XT2.

FWIW we call it "query repeatability", but to a certain extent it's the same thing as functional "referential integrity", with the current time effectively being passed as a parameter rather than being an implicit side-effect

oh I love that explanation, thank you

I'm preparing a talk on how we're using AWS Neptune to answer questions about the future state of the airline where I work, and I want to acknowledge XTDB in my talk

ah, interesting - give us a shout when that's released (if it's a public talk, of course!), will have a watch 🙂

Certainly 😁

It was my first public talk 😁

awesome! congratulations - and thanks for sharing here 🙂

🙏

Really interesting use case too - future-time queries via Gremlin...I bet there's quite a few orgs wanting that

Thank you for the kind words!

@USDPTD3FY Congrats on your fantastic presentation! The Southwest crew scheduling system meltdown is featured in my new book, Wiring the Winning Organization that comes out in a month, as one of the most astounding examples of a control overlay being unable to keep up with the performance environment. What an incredibly important capability you’re helping create for SWA!

Thank you for watching my talk and for your kind words!

Credit to the larger team, and to leadership, we are responding to our failures and we are taking this opportunity to mature our toolset so that the guarantees that we maintain to our customers are always upheld

Your words are a huge compliment! thank you