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

   OrToIn extract mode dropped "slot = c" / "slot IN (...)" candidates whose 
slot is also referenced by sibling conjuncts, e.g. an IN inferred from a kept 
inner OR. So "spm IN (...)" could not be inferred from nested multi-column ORs, 
and parquet lazy materialization decoded large JSON columns on nearly all rows.
   
   Skip the independence check for plain-slot candidates in extract mode only. 
The inferred IN is implied by the OR and the OR is kept, so results are 
unchanged. Add FE config enable_or_to_in_shared_slot_inference (default true, 
mutable) as a rollback switch covering only this change.
   
   ### What problem does this PR solve?
   
   Issue Number: close #xxx
   
   Related PR: #xxx
   
   Problem Summary:
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [x] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [ ] No need to test or manual test. Explain why:
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] Previous test can cover this change.
           - [ ] No code files have been changed.
           - [ ] Other reason <!-- Add your reason?  -->
   
   - Behavior changed:
       - [ ] No.
       - [ ] Yes. <!-- Explain the behavior change -->
   
   - Does this need documentation?
       - [ ] 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