You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Rajesh Balamohan (Jira)" <ji...@apache.org> on 2020/10/13 02:10:00 UTC
[jira] [Resolved] (HIVE-24234) Improve checkHashModeEfficiency in
VectorGroupByOperator
[ https://issues.apache.org/jira/browse/HIVE-24234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajesh Balamohan resolved HIVE-24234.
-------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
> Improve checkHashModeEfficiency in VectorGroupByOperator
> --------------------------------------------------------
>
> Key: HIVE-24234
> URL: https://issues.apache.org/jira/browse/HIVE-24234
> Project: Hive
> Issue Type: Improvement
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-24234.wip.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, {{VectorGroupByOperator::checkHashModeEfficiency}} compares the number of entries with the number input records that have been processed. For grouping sets, it accounts for grouping set length as well.
> Issue is that, the condition becomes invalid after processing large number of input records. This prevents the system from switching over to streaming mode.
> e.g Assume 500,000 input records processed, with 9 grouping sets, with 100,000 entries in hashtable. Hashtable would never cross 4,500,0000 entries as the max size itself is 1M by default.
> It would be good to compare the input records (adjusted for grouping sets) with number of output records (along with size of hashtable size) to determine hashing or streaming mode.
> E.g Q67.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)