Re: [I] Add Multi-Table Transaction API [iceberg]

2025-07-03 Thread via GitHub
nastra commented on issue #10617: URL: https://github.com/apache/iceberg/issues/10617#issuecomment-3031426120 @heman026 I didn't have resources to get back to this proposal but there's another proposal being discussed here: https://lists.apache.org/thread/r5otylsrm4txd4oxyv7c6scdwrbolck9

Re: [I] Add Multi-Table Transaction API [iceberg]

2025-07-02 Thread via GitHub
heman026 commented on issue #10617: URL: https://github.com/apache/iceberg/issues/10617#issuecomment-3030852336 Guys Any update on Multi-table Transactions progress -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use t

Re: [I] Add Multi-Table Transaction API [iceberg]

2024-12-30 Thread via GitHub
github-actions[bot] commented on issue #10617: URL: https://github.com/apache/iceberg/issues/10617#issuecomment-2566026989 This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occur

Re: [I] Add Multi-Table Transaction API [iceberg]

2024-07-02 Thread via GitHub
nastra commented on issue #10617: URL: https://github.com/apache/iceberg/issues/10617#issuecomment-2205193743 > So just to be clear, this will be only for the REST catalog right? Do we consider this feature also for other catalogs? Because I see you write that in the Google doc "Implementin

Re: [I] Add Multi-Table Transaction API [iceberg]

2024-07-02 Thread via GitHub
jackye1995 commented on issue #10617: URL: https://github.com/apache/iceberg/issues/10617#issuecomment-2203892955 > I don't recall that we have concluded on just doing a multi-table commit. yeah that's probably just my misunderstanding, since multi-table commit was what was eventually