Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

Forgot to attach a link to the update proposal <https://docs.google.com/document/d/1KVgUJc1WgftHfLz118vMbEE7HV8_pUDk4s-GJFDyAOE/edit?pli=1&tab=t.0#heading=h.ypbwvr181qn4> . On Tue, May 27, 2025 at 1:06 AM Maninderjit Singh < parmar.maninder...@gmail.com> wrote: > Hi com

Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

25 at 12:47 AM Péter Váry wrote: > I'm interested, but can't be there, but please record the meeting. > Thanks, > Peter > > Maninderjit Singh ezt írta (időpont: 2025. > máj. 24., Szo, 2:30): > >> Hi dev community, >> I was wondering if we could join a

Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

eberg multi-table transactions Friday, May 30 · 9:00 – 10:00am Time zone: America/Los_Angeles Google Meet joining info Video call link: https://meet.google.com/ffc-ttjs-vti On Wed, May 21, 2025 at 10:25 AM Maninderjit Singh < parmar.maninder...@gmail.com> wrote: > Hi dev community, > Fo

Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

4. Could not be extended to use in other proposals for causal reasoning. Thanks, Maninder On Tue, May 20, 2025 at 8:16 PM Maninderjit Singh < parmar.maninder...@gmail.com> wrote: > Appreciate the feedback on the "catalog-authored timestamp" document

Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

Blue wrote: >> >>> Hi everyone, >>> >>> To avoid passing copies of a file around for comments, I put the doc for >>> commit sequence numbers into Google so we can comment on a central copy: >>> https://docs.google.com/document/d/1jr4Ah8oceOmo6fwxG_0II4vKDUHUKSc

Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

Thanks for the updated proposal Drew! My preference for using the catalog authored timestamp is to minimize changes to the REST spec so we can have good backwards compatibility. I have quickly put together a draft proposal on how this should work. Looking forward to feedback and discussion. Draft

Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

it timestamps and evaluation functions > like NOW() locally, so Logical clock/SequenceNumber would be a more clear > approach to establish order of events across tables. What do you think? > > -Jagdeep > > On Thu, May 1, 2025 at 5:49 AM Maninderjit Singh < > parmar.maninder...@gmail.co

Proposal: Support Cascading Deletion of Namespaces

Hi all, We recently discussed the need for supporting cascading drop for the namespaces in the iceberg Catalog community sync to allow different catalog implementations to precisely define their behavior. I have added a short proposal

Re: Discuss proposal - IRC APIs for Multi-Statement Multi-Table Transactions

Thanks for starting the discussion! I wanted to discuss more about the "Catalog GlobalSequenceNumber". I think we not only need to order the snapshots across tables but also assign them some timestamp so that time travel queries also work consistently across tables. In other words, "Catalog Global