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

   Problem Summary:
   
   A `Project` above a `Join` may contain an item which reads no input, e.g. 
the constant that constant
   propagation materializes (`'014' AS org_code#6`), `now()`, or `1 + 1`. When 
such an item is pushed into
   one side of the join while the join condition still refers to the same 
exprId, both children of the join
   end up outputting that exprId.
   
   `PhysicalHashJoin#getHashConjunctsExprIds` splits the join keys by exprId 
only and checks the left side
   first, so both keys are attributed to the left child, the required hash spec 
of the right child stays
   empty, and `ChildrenPropertiesRegulator#calAnotherSideRequiredShuffleIds` 
fails with `ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 0
   `
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [ ] 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