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

Hive QA commented on HIVE-11387:
--------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12749640/HIVE-11387.07.patch

{color:green}SUCCESS:{color} +1 9347 tests passed

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4910/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4910/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-4910/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12749640 - PreCommit-HIVE-TRUNK-Build

> CBO: Calcite Operator To Hive Operator (Calcite Return Path) : fix 
> reduce_deduplicate optimization
> --------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-11387
>                 URL: https://issues.apache.org/jira/browse/HIVE-11387
>             Project: Hive
>          Issue Type: Sub-task
>          Components: CBO
>            Reporter: Pengcheng Xiong
>            Assignee: Pengcheng Xiong
>         Attachments: HIVE-11387.01.patch, HIVE-11387.02.patch, 
> HIVE-11387.03.patch, HIVE-11387.04.patch, HIVE-11387.05.patch, 
> HIVE-11387.06.patch, HIVE-11387.07.patch
>
>
> The main problem is that, due to return path, now we may have 
> {{(RS1-GBY2)\-(RS3-GBY4)}} when map.aggr=false, i.e., no map aggr. However, 
> in the non-return path, it will be treated as {{(RS1)-(GBY2-RS3-GBY4)}}. The 
> main problem is that it does not take into account of the setting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to