[
https://issues.apache.org/jira/browse/HIVE-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493124#comment-16493124
]
anishek edited comment on HIVE-18866 at 5/29/18 6:08 AM:
---------------------------------------------------------
[~sershe] the commit to branch-3 has hive-storage-api still points to
2.7-SNAPSHOT. shouldn't it be 3.1-SNAPSHOT. There seems to be failure in
branch-3 patches because the hive-jmh module compilation is failing with
hive-storage-api dependency of 2.7-SNAPSHOT.
Looks like you were going to file a jira, is that filed ? committed ?
cc [~thejas]
was (Author: anishek):
[~sershe] the commit to branch-3 has hive-storage-api still points to
2.7-SNAPSHOT. shouldn't it be 3.1-SNAPSHOT. There seems to be failure in
branch-3 patches because the hive-jmh module compilation is failing with
hive-storage-api dependency of 2.7-SNAPSHOT.
> Semijoin and analyze: Implement a Long -> Hash64 vector fast-path
> -----------------------------------------------------------------
>
> Key: HIVE-18866
> URL: https://issues.apache.org/jira/browse/HIVE-18866
> Project: Hive
> Issue Type: Improvement
> Components: Vectorization
> Reporter: Gopal V
> Assignee: Gopal V
> Priority: Major
> Labels: performance
> Fix For: 3.1.0, 4.0.0
>
> Attachments: 0001-hash64-WIP.patch, HIVE-18866.01.patch,
> HIVE-18866.02.patch, HIVE-18866.03.patch, HIVE-18866.04.patch,
> HIVE-18866.patch, perf-hash64-long.png
>
>
> A significant amount of CPU is wasted with JMM restrictions on byte[] arrays.
> To transform from one Long -> another Long, this goes into a byte[] array,
> which shows up as a hotspot.
> !perf-hash64-long.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
