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

Hive QA commented on HIVE-19824:
--------------------------------



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

{color:green}SUCCESS:{color} +1 due to 6 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14521 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/11750/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11750/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11750/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12927449 - 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.01.patch, HIVE-19824.01wip01.patch, 
> HIVE-19824.01wip01.patch, HIVE-19824.02.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)

Reply via email to