[core] Introduce a vector read planner for data evolution - #9877
Merged
JingsongLi merged 1 commit intoSep 17, 2026
Merged
Conversation
Contributor
|
+1 |
Contributor
|
I ran the affected tests locally at this head ( The planner reads well: the boundary sweep and the latest-provider-per-row-id resolution handle the overlapping vector file cases the previous sequential grouping could not, the "presence in writeCols" rule correctly documents explicit-NULL-overwrite behavior, and the column-pruning fallback (retain an active provider where the projected vector is not yet populated) closes the missing-range case. The three new tests cover shared-file partial updates, compacted ranges, and missing vector ranges. |
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.
Purpose
close #9876
Tests