[
https://issues.apache.org/jira/browse/HIVE-16151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960802#comment-15960802
]
Hive QA commented on HIVE-16151:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12862414/HIVE-16151.01.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 10579 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[drop_with_concurrency]
(batchId=235)
org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[escape_comments]
(batchId=235)
org.apache.hive.jdbc.TestJdbcDriver2.testResultSetMetaData (batchId=221)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/4606/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/4606/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-4606/
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: 3 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12862414 - PreCommit-HIVE-Build
> BytesBytesHashTable allocates large arrays
> ------------------------------------------
>
> Key: HIVE-16151
> URL: https://issues.apache.org/jira/browse/HIVE-16151
> Project: Hive
> Issue Type: Bug
> Reporter: Prasanth Jayachandran
> Assignee: Sergey Shelukhin
> Attachments: HIVE-16151.01.patch, HIVE-16151.patch
>
>
> These arrays cause GC pressure and also impose key count limitations on the
> table. Wrt the latter, we won't be able to get rid of it without a 64-bit
> hash function, but for now we can get rid of the former. If we need the
> latter we'd add murmur64 and probably account for it differently for resize
> (we don't want to blow up the hashtable by 4 bytes/key in the common case
> where #of keys is less than ~1.5B :))
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
