[
https://issues.apache.org/jira/browse/HIVE-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649654#comment-16649654
]
Hive QA commented on HIVE-17043:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12943846/HIVE-17043.16.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15079 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14460/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14460/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14460/
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: 12943846 - PreCommit-HIVE-Build
> Remove non unique columns from group by keys if not referenced later
> --------------------------------------------------------------------
>
> Key: HIVE-17043
> URL: https://issues.apache.org/jira/browse/HIVE-17043
> Project: Hive
> Issue Type: Sub-task
> Components: Logical Optimizer
> Affects Versions: 3.0.0
> Reporter: Ashutosh Chauhan
> Assignee: Vineet Garg
> Priority: Major
> Attachments: HIVE-17043.1.patch, HIVE-17043.10.patch,
> HIVE-17043.11.patch, HIVE-17043.12.patch, HIVE-17043.13.patch,
> HIVE-17043.14.patch, HIVE-17043.15.patch, HIVE-17043.16.patch,
> HIVE-17043.2.patch, HIVE-17043.3.patch, HIVE-17043.4.patch,
> HIVE-17043.5.patch, HIVE-17043.6.patch, HIVE-17043.7.patch,
> HIVE-17043.8.patch, HIVE-17043.9.patch
>
>
> Group by keys may be a mix of unique (or primary) keys and regular columns.
> In such cases presence of regular column won't alter cardinality of groups.
> So, if regular columns are not referenced later, they can be dropped from
> group by keys. Depending on operator tree may result in those columns not
> being read at all from disk in best case. In worst case, we will avoid
> shuffling and sorting regular columns from mapper to reducer, which still
> could be substantial CPU and network savings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
