[ZF_DRAFT][SPARK-54419][SS] Offline Repartition State Reader Support Multi-column Familes#5
Draft
[ZF_DRAFT][SPARK-54419][SS] Offline Repartition State Reader Support Multi-column Familes#5
Conversation
3fe17e9 to
5785a09
Compare
609ab21 to
aead185
Compare
aead185 to
482ed57
Compare
482ed57 to
f1807d7
Compare
17e1b25 to
c474783
Compare
67b547d to
b4fe10f
Compare
887f803 to
6cea08c
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request?
StatePartitionAllColumnFamiliesReader now supports operators with multiple column families. This includes
TransformWithState
Stream Stream Join V3
V3 works with RocksDB state store only, and uses a single state store instance per partition instead of 4. Each state store instance has 4 column families.
Why are the changes needed?
So that we can perform offline repartitioning for operators with multiple column families
Does this PR introduce any user-facing change?
How was this patch tested?
See added integration tests
Was this patch authored or co-authored using generative AI tooling?