[
https://issues.apache.org/jira/browse/HIVE-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966179#comment-13966179
]
Hive QA commented on HIVE-6873:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12639682/HIVE-6873.3.patch
{color:green}SUCCESS:{color} +1 5614 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/2216/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/2216/console
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: 12639682
> DISTINCT clause in aggregates is handled incorrectly by vectorized execution
> ----------------------------------------------------------------------------
>
> Key: HIVE-6873
> URL: https://issues.apache.org/jira/browse/HIVE-6873
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.13.0, 0.14.0
> Reporter: Remus Rusanu
> Assignee: Remus Rusanu
> Attachments: HIVE-6873.1.patch, HIVE-6873.2.patch, HIVE-6873.3.patch
>
>
> The vectorized aggregates ignore the DISTINCT clause. This cause incorrect
> results. Due to how GroupByOperatorDesc adds the DISTINCT keys to the overall
> aggregate keys the vectorized aggregates do account for the extra key, but
> they do not process the data correctly for the key. the reduce side the
> aggregates the input from the vectorized map side to results that are only
> sometimes correct but mostly incorrect. HIVE-4607 tracks the proper fix, but
> meantime I'm filing a bug to disable vectorized execution if DISTINCT is
> present. Fix is trivial.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
