[Draft](be) Unify storage reader column ordinals - #66472
Open
csun5285 wants to merge 1 commit into
Open
Conversation
csun5285
requested review from
924060929,
airborne12,
deardeng,
eldenmoon,
englefly,
gavinchou,
liaoxin01,
luwei16,
morrySnow,
starocean999 and
yiguolei
as code owners
August 5, 2026 06:26
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
csun5285
force-pushed
the
refactor/reader-return-columns
branch
from
August 7, 2026 12:14
e96085d to
6a3b439
Compare
### What problem does this PR solve? Issue Number: N/A Related PR: apache#66432 Problem Summary: Storage readers maintained FE block positions, tablet-schema column IDs, predicate IDs, and delete-predicate columns through parallel mappings. Projection, nested-column pruning, virtual expressions, and row-binlog dependencies could make those mappings diverge. Use one ordered read schema as the reader coordinate, keep expected materialization types alongside physical columns, append storage-only delete-predicate dependencies after FE slots, and preserve required row-binlog scan columns without changing the scan output contract. ### Release note Fix inconsistent storage-reader column mappings for projected and row-binlog scans. ### Check List (For Author) - Test: - ASAN BE and FE build - BE clang-format and format check - FE Checkstyle - Regression: row_binlog_p0, delete_p0, unique_seq_map_p0, and targeted schema-change/delete/sequence suites - Regression: variant_p0 code-related cases passed; one outfile case was blocked by invalid external OSS credentials - Behavior changed: Yes (reader column identity and row-binlog dependency handling are unified) - Does this need documentation: No
csun5285
force-pushed
the
refactor/reader-return-columns
branch
from
August 7, 2026 12:27
6a3b439 to
768a009
Compare
Contributor
Author
|
run buildall |
Contributor
TPC-H: Total hot run time: 29131 ms |
Contributor
FE UT Coverage ReportIncrement line coverage |
Contributor
TPC-DS: Total hot run time: 158453 ms |
Contributor
ClickBench: Total hot run time: 23.85 s |
Contributor
FE Regression Coverage ReportIncrement line coverage |
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 problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)