[core] Support latest snapshot delta scan in batch - #9142
Open
wwj6591812 wants to merge 1 commit into
Open
Conversation
wwj6591812
marked this pull request as ready for review
August 10, 2026 09:14
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.
Purpose
Batch pipelines sometimes need to process only the newest committed snapshot, but currently must first query its ID and construct
incremental-betweenboundaries.This adds
scan.mode = 'latest-delta'for batch sources. At planning time it selects the literal latest snapshotNand reuses the existing DELTA scanner for(N - 1, N].It deliberately does not search backwards for an APPEND snapshot. Therefore, if the latest snapshot is COMPACT or OVERWRITE, the query returns no records instead of treating rewritten files as new logical data. Streaming use is rejected, and boundary or time-travel companion options are rejected rather than ignored.
This is a convenience mode, not a persistent consumer cursor. Workflows that must consume multiple snapshots reliably should continue to use explicit
incremental-betweenboundaries or tags.Tests