Hi everyone, I remember a while ago we had some discussions regarding the multi-table transaction API introduced in the REST spec at https://github.com/apache/iceberg/pull/6948#discussion_r1244026460.
I recently did a more in-depth analysis, which can be viewed at: https://docs.google.com/document/d/10tfqETygf2BLA34CoZLxK3v5xk1BWUNKFA9WE8X_w-U/edit#heading=h.qv4y242f0g23 Based on the analysis, I think the current API would introduce some edge cases for enforcing ACID guarantees. It would be great if we can take a look into the analysis and see if the concern is legit or not. If it is indeed an issue, I also put a few items for the path forward to resolve those issues, which includes making corresponding fixes in engines like Trino and Spark, and potentially introducing a StartTransaction API in the REST spec. Really appreciate if anyone could take a look and give some feedback! Best, Jack Ye
