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

Hive QA commented on HIVE-10215:
--------------------------------



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

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

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 8692 tests executed
*Failed tests:*
{noformat}
TestMinimrCliDriver-smb_mapjoin_8.q - did not produce a TEST-*.xml file
TestSparkClient - did not produce a TEST-*.xml file
org.apache.hadoop.hive.thrift.TestHadoop20SAuthBridge.testMetastoreProxyUser
org.apache.hadoop.hive.thrift.TestHadoop20SAuthBridge.testSaslWithHiveMetaStore
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3285/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3285/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3285/

Messages:
{noformat}
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: 12709403 - PreCommit-HIVE-TRUNK-Build

> Large IN() clauses: deep hashCode performance during optimizer pass
> -------------------------------------------------------------------
>
>                 Key: HIVE-10215
>                 URL: https://issues.apache.org/jira/browse/HIVE-10215
>             Project: Hive
>          Issue Type: Bug
>          Components: Logical Optimizer
>    Affects Versions: 1.2.0
>            Reporter: Gopal V
>            Assignee: Gopal V
>            Priority: Minor
>         Attachments: HIVE-10215.1.patch
>
>
> The logical optimizer uses several maps and sets, which are exceeding 
> expensive for large IN() clauses due to the fact that several part of the 
> queries walk over the lists without short-circuiting during hashCode(), while 
> equals() is faster due to short-circuiting via less expensive operators.



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

Reply via email to