[SPARK-55494][SS] Introduce iterator/prefixScan with multi-values in StateStore API #54278
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
…projection, some tests are failing
Contributor
Author
|
The last commit is only relevant to this PR. Once #53911 is merged, I will rebase this PR to remove commits except this one. |
HeartSaVioR
force-pushed
the
SPARK-55494
branch
2 times, most recently
from
503f10d to
c6bbfe8
Compare
HeartSaVioR
force-pushed
the
SPARK-55494
branch
from
c6bbfe8 to
3690934
Compare
…e included in other PR" This reverts commit 314acd4.
HeartSaVioR
force-pushed
the
SPARK-55494
branch
from
3690934 to
0c5b92d
Compare
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?
This PR proposes to introduce iterator/prefixScan with multi-values in StateStore API.
Why are the changes needed?
The functionality is missing on StateStore API so when the caller sets multi-values for specific CF, that CF doesn't support scanning through the data. The new functionality will be used in new state format version in stream-stream join, specifically SPARK-55144 (#53930).
Does this PR introduce any user-facing change?
No.
How was this patch tested?
New UTs.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: claude-4.5-sonnet
The above is used for creating a new test suite. All other parts aren't generated by LLM.