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

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: #64242
   
   Problem Summary:
   
   Backport #64242 to branch-4.1. Preserve nested access paths for TopN lazy 
materialization rowid fetch, avoid row-store fetch when lazy slots carry nested 
access paths, and keep struct iterators readable when child fields are pruned.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [ ] Unit Test
       - [x] Manual test (add detailed scripts or steps below)
           - `git diff --check HEAD^ HEAD`
       - [x] No need to test or manual test. Explain why:
           - [x] Previous test can cover this change. This is a clean backport 
of #64242; the original PR added FE UT and regression coverage.
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] No code files have been changed.
           - [ ] Other reason <!-- Add your reason?  -->
   
   - Behavior changed:
       - [x] No.
       - [ ] Yes. <!-- Explain the behavior change -->
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes. <!-- Add document PR link here. eg: 
https://github.com/apache/doris-website/pull/1214 -->
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label <!-- Add branch pick label that this PR should 
merge into -->
   


-- 
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