[ 
https://issues.apache.org/jira/browse/HIVE-23882?focusedWorklogId=547097&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-547097
 ]

ASF GitHub Bot logged work on HIVE-23882:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Feb/21 16:20
            Start Date: 03/Feb/21 16:20
    Worklog Time Spent: 10m 
      Work Description: kgyrtkirk commented on a change in pull request #1286:
URL: https://github.com/apache/hive/pull/1286#discussion_r569549445



##########
File path: ql/src/java/org/apache/hadoop/hive/ql/exec/OperatorUtils.java
##########
@@ -654,11 +655,18 @@ public static String findTableColNameOf(Operator<?> 
start, String internalColNam
         continue;
       }
       // If columnName is the output of a ColumnExpr get the original 
columnName from the Expr Map
-      if (currentOp.getColumnExprMap() != null && 
currentOp.getColumnExprMap().containsKey(internalColName)
-              && currentOp.getColumnExprMap().get(internalColName) instanceof 
ExprNodeColumnDesc) {
-        internalColName = ((ExprNodeColumnDesc) 
currentOp.getColumnExprMap().get(internalColName)).getColumn();
+      if (currentOp.getColumnExprMap() != null && 
currentOp.getColumnExprMap().containsKey(internalColName)) {
+        // Only use colInfo that is ExprNodeColumnDesc (could even be a UDF on 
the key at this point)
+        if (currentOp.getColumnExprMap().get(internalColName) instanceof 
ExprNodeColumnDesc) {
+          internalColName = ((ExprNodeColumnDesc) 
currentOp.getColumnExprMap().get(internalColName)).getColumn();
+          keyColInfo = currentOp.getSchema().getColumnInfo(internalColName);

Review comment:
       this doesn't look right to me; these 2 lines are mapping back to the 
previous ops colname and look it up on the current operator - if this does fix 
some issue for you ; then I guess there were already some issue with the 
mapping/schema - I think the original bug should be fixed in this case; because 
the output of the above loopback might be undefined
   
   I think this fix may cause troubles later...




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

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


Issue Time Tracking
-------------------

    Worklog Id:     (was: 547097)
    Time Spent: 1h 20m  (was: 1h 10m)

> Compiler should skip MJ keyExpr for probe optimization
> ------------------------------------------------------
>
>                 Key: HIVE-23882
>                 URL: https://issues.apache.org/jira/browse/HIVE-23882
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Panagiotis Garefalakis
>            Assignee: Panagiotis Garefalakis
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> In probe we cannot currently support Key expressions (on the big table Side) 
> as ORC CVs Probe directly the smalltable HT (there is no expr evaluation at 
> that level).
> TezCompiler should take this into account when picking MJs to push probe 
> details



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to