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

Hive QA commented on HIVE-14437:
--------------------------------



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

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 10440 tests 
executed
*Failed tests:*
{noformat}
TestMsgBusConnection - did not produce a TEST-*.xml file
TestQueryLifeTimeHook - did not produce a TEST-*.xml file
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver_orc_llap_counters
org.apache.hive.jdbc.TestJdbcWithMiniHS2.testAddJarConstructorUnCaching
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-MASTER-Build/788/testReport
Console output: 
https://builds.apache.org/job/PreCommit-HIVE-MASTER-Build/788/console
Test logs: 
http://ec2-204-236-174-241.us-west-1.compute.amazonaws.com/logs/PreCommit-HIVE-MASTER-Build-788/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
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: 4 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12822280 - PreCommit-HIVE-MASTER-Build

> Vectorization: Optimize key misses in VectorMapJoinFastBytesHashTable
> ---------------------------------------------------------------------
>
>                 Key: HIVE-14437
>                 URL: https://issues.apache.org/jira/browse/HIVE-14437
>             Project: Hive
>          Issue Type: Improvement
>          Components: Vectorization
>    Affects Versions: 2.2.0
>            Reporter: Gopal V
>            Assignee: Gopal V
>         Attachments: HIVE-14437.1.patch
>
>
> Currently, the lookup in VectorMapJoinFastBytesHashTable proceeds until the 
> max number of metric put conflicts have been reached.
> This can have a fast-exit when encountering the first empty slot during the 
> probe, to speed up looking for non-existent keys.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to