feat: refresh table when committing to support concurrent appends#1885
feat: refresh table when committing to support concurrent appends#1885YinZheng-Sun wants to merge 1 commit intoapache:mainfrom
Conversation
YinZheng-Sun
changed the title
|
Thanks @YinZheng-Sun for working on this. It looks like it is a duplicate of #1772 |
Yes, this PR is inspired by #1772 and #1678. I want to accelerate the progress of this feature and have fixed the UTs |
|
I've created some subtasks on #819 that will help us implement the required validation functions that we can invoke to check that no conflicting commits have been made between two snapshots. @YinZheng-Sun would you be interested in helping out with some of those implementations? |
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that's incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
3 participants
Rationale for this change
Support for Concurrent Append Operations
Refresh Table
If changes in the table's metadata are detected (indicating that other transactions have been committed during this period), update the table's metadata and the current parent_snapshot_id.
If no changes are detected, proceed with the normal commit.
Are these changes tested?
UT
Are there any user-facing changes?