[SPARK-56798][SQL][DOCS] Clarify streaming CDC emission timing and netChanges scope#55776
Open
gengliangwang wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-56798][SQL][DOCS] Clarify streaming CDC emission timing and netChanges scope#55776gengliangwang wants to merge 1 commit intoapache:masterfrom
gengliangwang wants to merge 1 commit intoapache:masterfrom
Conversation
…tChanges scope Address two follow-up review threads on PR apache#55637 (streaming CDC netChanges): - The "held back" paragraph was worded as if the one-commit emission lag were a netChanges-specific property. It is not -- carry-over removal and update detection use append-mode `Aggregate` keyed on `_commit_timestamp` and have the same lag as the netChanges `transformWithState` timer. - Set realistic expectations for streaming netChanges: for typical CDC sources that produce at most one change per row per commit, the streaming output equals what `computeUpdates` would produce, because only one commit's changes are buffered at a time. Cross-commit merging only kicks in when several commits touch the same row before the older one's output is emitted. Direct users to a batch read for full-range collapse. Both points are now stated up-front in plain language, with a bulleted list and short bold labels for scannability.
Member
Author
|
cc @johanl-db |
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?
Address two follow-up review threads on PR #55637 (streaming CDC netChanges) by clarifying the streaming behavior in the
ChangelogJavadoc.The previous paragraph read as if the one-commit emission lag were a netChanges-specific property; in fact carry-over removal and update detection use append-mode
Aggregatekeyed on_commit_timestampand have the same lag as the netChangestransformWithStatetimer. The paragraph also did not set expectations for what streaming netChanges actually collapses in practice.Replaced the existing single paragraph with a bulleted list:
computeUpdates. Multiple commits' changes are merged only when those commits touch the same row before the older one's output has been emitted. For full-range collapse, use a batch read.This is a sub-task of SPARK-55668.
Why are the changes needed?
Spelling out the emission timing and the practical netChanges scope prevents adopters from forming wrong expectations about what streaming netChanges does for typical (atomic-commit) CDC workloads. Naming the lag and the buffer-window scope explicitly also makes the doc consistent with the implementation, where both facts are properties of all three streaming post-processing paths.
Does this PR introduce any user-facing change?
Documentation only. No behavior change.
How was this patch tested?
Doc-only change.
Xdoclint:html,syntax,accessibilityis clean onChangelog.java(errors limited to expected "cannot find symbol" without classpath). No code changed; existing CDC test suites unaffected.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude opus-4-7