[ 
https://issues.apache.org/jira/browse/HIVE-20983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928310#comment-16928310
 ] 

Hive QA commented on HIVE-20983:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12980114/HIVE-20983.2.patch

{color:green}SUCCESS:{color} +1 due to 7 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 16752 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/18555/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/18555/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-18555/

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: 12980114 - PreCommit-HIVE-Build

> Vectorization: Scale up small hashtables, when collisions are detected
> ----------------------------------------------------------------------
>
>                 Key: HIVE-20983
>                 URL: https://issues.apache.org/jira/browse/HIVE-20983
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gopal V
>            Assignee: Mustafa Iman
>            Priority: Major
>         Attachments: HIVE-20983.1.patch, HIVE-20983.2.patch
>
>
> Hive's hashtable estimates are getting better with HyperLogLog stats in 
> place, but an accurate estimate does not always result in a low number of 
> collisions.
> The hashtables which contain a very small number of items tend to lose their 
> O(1) lookup performance where there are collisions. Since collisions are easy 
> to detect within the fast hashtable implementation, a rehashing to a higher 
> size will help these small hashtables avoid collisions and go back to O(1) 
> perf.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to