[
https://issues.apache.org/jira/browse/HIVE-23953?focusedWorklogId=466073&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-466073
]
ASF GitHub Bot logged work on HIVE-23953:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Aug/20 07:20
Start Date: 04/Aug/20 07:20
Worklog Time Spent: 10m
Work Description: rbalamohan commented on pull request #1340:
URL: https://github.com/apache/hive/pull/1340#issuecomment-668426658
LGTM. +1 pending tests.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 466073)
Time Spent: 0.5h (was: 20m)
> Use task counter information to compute keycount during hashtable loading
> -------------------------------------------------------------------------
>
> Key: HIVE-23953
> URL: https://issues.apache.org/jira/browse/HIVE-23953
> Project: Hive
> Issue Type: Bug
> Reporter: Rajesh Balamohan
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There are cases when compiler misestimates key count and this results in a
> number of hashtable resizes during runtime.
> [https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/exec/vector/mapjoin/fast/VectorMapJoinFastHashTableLoader.java#L128]
> In such cases, it would be good to get "approximate_input_records" (TEZ-4207)
> counter from upstream to compute the key count more accurately at runtime.
>
> *
> *
> Options
> h4.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
