[SPARK-54420][SS] Introduce StatePartitionWriter for Offline Repartitioning #53287
+1,717
−33
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Introducing StatePartitionAllColumnFamiliesWriter as part of the offline repartition project. In this PR, we only support a single-column-family operator.
This writer takes the repartitioned DataFrame returned from StatePartitionAllColumnFamiliesReader and writes it to a new version in the state store. See the comments for the DataFrame schema. In addition, this writer does not load previous state (since we are overwriting the state with the repartitioned data), and when committing, it will always commit a snapshot.
Major Changes
Why are the changes needed?
This will be used in offline repartitioning to allow OfflineRepartitioningRunner to directly write data to state store
Does this PR introduce any user-facing change?
No
How was this patch tested?
Integration tests in
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/v2/state/StatePartitionAllColumnFamiliesWriterSuite.scalaUnit tests in
sql/core/src/test/scala/org/apache/spark/sql/execution/streaming/state/RocksDBSuite.scalaWas this patch authored or co-authored using generative AI tooling?
Yes. Sonnet 4.5