Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Let me close the opaque id option with you and then I will send an invite for broader discussion with the community (hopefully in next week or so). Thanks, Maninder On Fri, Jun 27, 2025 at 11:34 AM Dmitri Bourlatchkov wrote: > Thanks, Maninder! Good idea. > > Is any meeting for this already sch

Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Thanks, Maninder! Good idea. Is any meeting for this already scheduled? Cheers, Dmitri. On Fri, Jun 27, 2025 at 1:52 AM Maninderjit Singh < parmar.maninder...@gmail.com> wrote: > Thanks Dmitri! > I will add this to the doc. Also, it might be a good idea to discuss it in > a meeting so we can ha

Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Thanks Dmitri! I will add this to the doc. Also, it might be a good idea to discuss it in a meeting so we can hash out the details. On Wed, Jun 25, 2025, 9:23 AM Dmitri Bourlatchkov wrote: > Hi Maninder, > > Thanks for adding a section on opaque IDs and apologies for delayed reply > from my side

Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Hi Maninder, Thanks for adding a section on opaque IDs and apologies for delayed reply from my side. I could not find a place where to fit my text in the doc, so I'm sending it in this email :) This option is mostly related to option 2 (CSN) but proposes to use commit IDs (alternative to CSN) tha

Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Hi Dmitri, By "chatty protocol" in my last email, I meant it would lead to multiple Catalog calls for simple read queries. I also wrote this down under alternatives considered in

Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Thanks Dmitri for the review! We have been deliberate about not including server side implementation for brevity and to allow each vendor to choose the best option for them. Having said that, I have included a few papers that you can reference. I have also added a new

Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Thanks for the quick response, Jagdeep! I can certainly add a section to the doc. Could you clarify what you mean by "chatty protocol", though. I did not find that term in the linked email discussion :) Thanks, Dmitri. On Thu, Jun 19, 2025 at 2:28 PM Jagdeep Sidhu wrote: > Hi Dmitri, > > Thank

Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Hi Dmitri, Thank you for reviewing. As you said, we previously explored and dropped TransactionContext APIs with opaque IDs because it created a very chatty protocol and also led to complex transaction state management on Server side, link to old thread below. Would you add a section to the exist

Re: [DISCUSS] Multi-statement multi-transaction proposal for Apache REST Catalog

Thanks for driving this proposal, Maninder! >From my POV the need for Catalogs to provide a monotonic sequence number has deep implications on the catalog implementations. I added a related comment to the doc as well. The document does a good job at discussing the client operation. I'd appreciate