hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-6873) DISTINCT clause in aggregates is handled incorrectly by vectorized execution
Date Thu, 10 Apr 2014 05:49:15 GMT


Hive QA commented on HIVE-6873:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 5570 tests executed
*Failed tests:*

Test results:
Console output:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed

This message is automatically generated.


> DISTINCT clause in aggregates is handled incorrectly by vectorized execution
> ----------------------------------------------------------------------------
>                 Key: HIVE-6873
>                 URL:
>             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
> 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

View raw message