[
https://issues.apache.org/jira/browse/HIVE-19824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506753#comment-16506753
]
Hive QA commented on HIVE-19824:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12926898/HIVE-19824.01wip01.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/11639/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11639/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11639/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12926898/HIVE-19824.01wip01.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12926898 - PreCommit-HIVE-Build
> Improve online datasize estimations for MapJoins
> ------------------------------------------------
>
> Key: HIVE-19824
> URL: https://issues.apache.org/jira/browse/HIVE-19824
> Project: Hive
> Issue Type: Improvement
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Attachments: HIVE-19824.01wip01.patch, HIVE-19824.01wip01.patch
>
>
> Statistics.datasize() only accounts for "real" data size; but for example
> handling 1M rows might introduce some datastructure overhead...if the "real"
> data is small - even this overhead might become the real memory usage
> for 6.5M rows of (int,int) the estimation is 52MB
> in reality this eats up ~260MB from which 210MB is used to service the
> hashmap functionality to that many rows.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
