Spark 3.x: Support rewrite data files with starting sequence number #4701
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rajarshisarkar
force-pushed
the
rewrite-data-files-with-starting-sequence-number
branch
from
92d29b8 to
9e4a797
Compare
RussellSpitzer
approved these changes
May 5, 2022
Member
|
Thanks @rajarshisarkar ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that
use-starting-sequence-numberoption is missing while developing #4377 and #4579. Adding support for the same in this PR.When
use-starting-sequence-numberis enabled then compaction should use the sequence number of the snapshot at compaction start time for new data files, instead of using the sequence number of the newly produced snapshot. This avoids commit conflicts with updates that add newer equality deletes at a higher sequence number.cc: @RussellSpitzer @jackye1995 @szehon-ho