[
https://issues.apache.org/jira/browse/HIVE-21007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710734#comment-16710734
]
Hive QA commented on HIVE-21007:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12950749/HIVE-21007.2.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15649 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/15187/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/15187/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-15187/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12950749 - PreCommit-HIVE-Build
> Semi join + Union can lead to wrong plans
> -----------------------------------------
>
> Key: HIVE-21007
> URL: https://issues.apache.org/jira/browse/HIVE-21007
> Project: Hive
> Issue Type: Bug
> Reporter: Vineet Garg
> Assignee: Vineet Garg
> Priority: Major
> Attachments: HIVE-21007.1.patch, HIVE-21007.2.patch
>
>
> Tez compiler has the ability to push JOIN within UNION (by replicating join
> on each branch). If this JOIN had a SJ branch outgoing (or incoming) it could
> mess up the plan and end up generating incorrect or wrong plan.
> As a safe measure any SJ branch after UNION should be removed (until we
> improve the logic to better handle SJ branches)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
