[ https://issues.apache.org/jira/browse/HIVE-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099514#comment-14099514 ]
Hive QA commented on HIVE-7617: ------------------------------- {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/12662221/HIVE-7617.03.patch {color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 5817 tests executed *Failed tests:* {noformat} org.apache.hive.jdbc.miniHS2.TestHiveServer2.testConnection {noformat} Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/358/testReport Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/358/console Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-358/ 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: 1 tests failed {noformat} This message is automatically generated. ATTACHMENT ID: 12662221 > optimize bytes mapjoin hash table read path wrt serialization, at least for > common cases > ---------------------------------------------------------------------------------------- > > Key: HIVE-7617 > URL: https://issues.apache.org/jira/browse/HIVE-7617 > Project: Hive > Issue Type: Improvement > Reporter: Sergey Shelukhin > Assignee: Sergey Shelukhin > Attachments: HIVE-7617.01.patch, HIVE-7617.02.patch, > HIVE-7617.03.patch, HIVE-7617.03.patch, HIVE-7617.04.patch, HIVE-7617.patch, > HIVE-7617.prelim.patch, hashmap-wb-fixes.png > > > BytesBytes has table stores keys in the byte array for compact > representation, however that means that the straightforward implementation of > lookups serializes lookup keys to byte arrays, which is relatively expensive. > We can either shortcut hashcode and compare for common types on read path > (integral types which would cover most of the real-world keys), or specialize > hashtable and from BytesBytes... create LongBytes, StringBytes, or whatever. > First one seems simpler now. -- This message was sent by Atlassian JIRA (v6.2#6252)