[SPARK-55510] Update structured-streaming-state-data-source.md doc to reflect deleteRange#54548
Open
zeruibao wants to merge 1 commit intoapache:masterfrom
Open
Conversation
| ### Reading state changes over microbatches | ||
|
|
||
| If we want to understand the change of state store over microbatches instead of the whole state store at a particular microbatch, 'readChangeFeed' is the option to use. | ||
| For example, this is the code to read the change of state from batch 2 to the latest committed batch. |
Contributor
There was a problem hiding this comment.
Lets add the note here actually
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
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.
What changes were proposed in this pull request?
Update structured-streaming-state-data-source.md to mention deleteRange do not support CDF stream
Why are the changes needed?
Currently, deleteRange does not support CDF. Need to update the doc.
Does this PR introduce any user-facing change?
No
How was this patch tested?
N/A
Was this patch authored or co-authored using generative AI tooling?
Cursor