hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yin Huai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4927) When we merge two MapJoin MapRedTasks, the TableScanOperator of the second one should be removed
Date Thu, 25 Jul 2013 16:43:49 GMT

    [ https://issues.apache.org/jira/browse/HIVE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719761#comment-13719761
] 

Yin Huai commented on HIVE-4927:
--------------------------------

HIVE-4927.D11811.2.patch is not based on the latest trunk. Please ignore it...
                
> When we merge two MapJoin MapRedTasks, the TableScanOperator of the second one should
be removed
> ------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-4927
>                 URL: https://issues.apache.org/jira/browse/HIVE-4927
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.12.0
>            Reporter: Yin Huai
>            Assignee: Yin Huai
>         Attachments: HIVE-4927.D11811.1.patch, HIVE-4927.D11811.2.patch, HIVE-4927.D11811.3.patch
>
>
> {code}
> set hive.auto.convert.join=true;
> set hive.auto.convert.join.noconditionaltask=true;
> EXPLAIN
> SELECT x1.key AS key FROM src x1 JOIN src1 y1 ON (x1.key = y1.key) JOIN src1 y2 ON (x1.value
= y2.value) GROUP BY x1.key;
> {\code}
> We will get a NPE from MetadataOnlyOptimizer. The reason is that the operator tree of
the MapRedTask evaluating two MapJoins is 
> {code}
> TS1->MapJoin1->TS2->MapJoin2->...
> {\code}
> We should remove the TS2...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message