[
https://issues.apache.org/jira/browse/HIVE-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695787#comment-14695787
]
Gopal V commented on HIVE-11502:
--------------------------------
bq. I do not see risk here. You can assume the LazyDouble as a vectorized
object which only has one element in it.
Changing a hashcode of an actual type breaks bucketed joins - the lhs & rhs of
the join has to use the exact same hashcode.
Vectorization overrides that inside VectorHashKeyWrapper, which serves as a
model for this fix.
The new hash computation needs to only go in place of the Arrays.hashCode() in
the ListKeyWrapper - so that the only exposure to the uniform hashCode is
within map-side aggregation.
> Map side aggregation is extremely slow
> --------------------------------------
>
> Key: HIVE-11502
> URL: https://issues.apache.org/jira/browse/HIVE-11502
> Project: Hive
> Issue Type: Bug
> Components: Logical Optimizer, Physical Optimizer
> Affects Versions: 1.2.0
> Reporter: Yongzhi Chen
> Assignee: Yongzhi Chen
> Attachments: HIVE-11502.1.patch
>
>
> For the query as following:
> {noformat}
> create table tbl2 as
> select col1, max(col2) as col2
> from tbl1 group by col1;
> {noformat}
> If the column for group by has many different values (for example 400000) and
> it is in type double, the map side aggregation is very slow. I ran the query
> which took more than 3 hours , after 3 hours, I have to kill the query.
> The same query can finish in 7 seconds, if I turn off map side aggregation by:
> {noformat}
> set hive.map.aggr = false;
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
