[SPARK-46709][SS] Expose partition_id column for state data source #44717
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
Contributor
Author
HeartSaVioR
changed the title
Contributor
|
@chaoqin-li1123 Could you please push an empty commit to retrigger GA build? I guess it is not related but let's give a try once more. Thanks in advance! |
HyukjinKwon
approved these changes
Jan 14, 2024
Member
HyukjinKwon
left a comment
HyukjinKwon
left a comment
There was a problem hiding this comment.
Test failure should be unrelated.
Member
|
Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What changes were proposed in this pull request?
Expose the partition_id column of state data source was hidden by default.
Why are the changes needed?
partition_id column is useful to users.
Does this PR introduce any user-facing change?
yes, Expose the partition_id column of state data source was hidden by default and modify the doc accordingly.
How was this patch tested?
Modify existing integration test.
Was this patch authored or co-authored using generative AI tooling?
No.