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

   # Proposed changes
   
   Issue Number: close #xxx
   
   ## Problem summary
   
   consider the query like this:
   ```sql
   SELECT
       k3, k4
   FROM
       test
   WHERE
       EXISTS( SELECT
               d.*
           FROM
               (SELECT
                   k1 AS _1234, SUM(k2)
               FROM
                   `test` d
               GROUP BY _1234) d
                   LEFT JOIN
               (SELECT
                   k1 AS _1234,
                       SUM(k2)
               FROM
                   `test`
               GROUP BY _1234) temp ON d._1234 = temp._1234) 
   ORDER BY k3, k4
   ```
   
   when we analyze group by exprs in `temp` inline view. we bind the `_1234` on 
`d._1234` by mistake.
   that because, when we do analyze in a **SUB-QUERY**, we will resolve SlotRef 
by itself **AND** parent's tuple. in the meanwhile, we register child's tuple 
to parent's analyzer. So, in a **SUB-QUERY**, the brother's tuple will affect 
the resolve result of current inlineview's slot.
   
   This PR:
   
   1. add a flag on the function `resolveColumnRef` in `Analyzer`
   ```java
   private TupleDescriptor resolveColumnRef(String colName, boolean 
requestFromChild);
   private TupleDescriptor resolveColumnRef(TableName tblName, String colName, 
boolean requestByChild);
   ``` 
   
   2. add a flag to specify whether the tuple is from child.
   ```java
   // alias name -> <from child, tupleDesc>
   private final Multimap<String, Pair<Boolean, TupleDescriptor>> tupleByAlias;
   ```
   
   when `requestByChild == true`, we **SKIP** the tuple from other child to 
avoid resolve error.
   
   
   ## Checklist(Required)
   
   * [ ] Does it affect the original behavior
   * [ ] Has unit tests been added
   * [ ] Has document been added or modified
   * [ ] Does it need to update dependencies
   * [ ] Is this PR support rollback (If NO, please explain WHY)
   
   ## Further comments
   
   If this is a relatively large or complex change, kick off the discussion at 
[d...@doris.apache.org](mailto:d...@doris.apache.org) by explaining why you 
chose the solution you did and what alternatives you considered, etc...
   
   


-- 
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: commits-unsubscr...@doris.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org

Reply via email to