mrhhsg opened a new pull request, #65355:
URL: https://github.com/apache/doris/pull/65355

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Problem Summary: Nested column pruning can lazily read only map keys or only 
map values after a sibling struct field is used for filtering. The map 
placeholder is cleared in the lazy phase, but the skipped key/value counterpart 
was left empty, so ColumnMap offsets no longer matched both child column sizes. 
This PR fills the skipped counterpart with defaults during lazy map 
materialization while still avoiding unnecessary child data reads.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test:
       - Unit Test: ./run-be-ut.sh --run 
--filter=ColumnReaderTest.MapLazyReadByRowidsFillsSkippedKeysForValuesOnlyPath
       - Regression test: doris-local-regression --network 10.26.20.3/24 all -d 
nereids_rules_p0/column_pruning -s struct_map_pruning_lazy_read -forceGenOut
       - Regression test: doris-local-regression --network 10.26.20.3/24 all -d 
nereids_rules_p0/column_pruning -s struct_map_pruning_lazy_read
       - Format: build-support/clang-format.sh 
be/src/storage/segment/column_reader.cpp 
be/test/storage/segment/column_reader_test.cpp
       - Static Check: git diff --check
       - Static Check: build-support/check-format.sh
       - Static Check: build-support/run-clang-tidy.sh --build-dir 
be/ut_build_ASAN --base HEAD (failed on existing unrelated clang-tidy analysis 
errors in included/current files)
   - Behavior changed: No
   - Does this need documentation: No
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to