[
https://issues.apache.org/jira/browse/HIVE-15955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878911#comment-15878911
]
Jason Dere commented on HIVE-15955:
-----------------------------------
I think this mostly looks good, though this misses one case - semijoin
optimizations (min/max/bloomfilter) generate an extra SEL-GBY-RS-GBY-RS branch,
but the last RS is never directly connected to the destination TableScan/Filter
which uses the min/max/bloomfilter. Instead there is a separate mapping kept in
the ParseContext to track these. This may require additional handling to call
setOutputOperators() for this SEL-GBY-RS-GBY-RS branch (which is also generated
during TezCompiler, so it might occur after the Optimizer rules have fired).
Should handling this be done in a separate Jira?
> make explain formatted to include opId and etc
> ----------------------------------------------
>
> Key: HIVE-15955
> URL: https://issues.apache.org/jira/browse/HIVE-15955
> Project: Hive
> Issue Type: New Feature
> Reporter: Pengcheng Xiong
> Assignee: Pengcheng Xiong
> Attachments: HIVE-15955.01.patch, HIVE-15955.02.patch,
> HIVE-15955.03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
