Core: Expose row lineage in ChangelogScanTask and changelog schema for v3+ tables - #17792
Open
hemanthboyina wants to merge 2 commits into
Open
Core: Expose row lineage in ChangelogScanTask and changelog schema for v3+ tables#17792hemanthboyina wants to merge 2 commits into
hemanthboyina wants to merge 2 commits into
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.
In row lineage every row gets a stable _row_id assigned at commit time. But the changelog scan never exposed it. You could scan for changes but had no way to know which row IDs were added or deleted, making it impossible to correlate changelog events with actual rows across snapshots.