You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2022/10/21 07:32:01 UTC
[jira] [Updated] (HIVE-14246) Tez: disable auto-reducer parallelism when CUSTOM_EDGE is in place
[ https://issues.apache.org/jira/browse/HIVE-14246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stamatis Zampetakis updated HIVE-14246:
---------------------------------------
Fix Version/s: (was: 3.2.0)
I cleared the fixVersion field since this ticket is not resolved. Please review this ticket and if the fix is already committed to a specific version please set the version accordingly and mark the ticket as RESOLVED.
According to the JIRA guidelines (https://cwiki.apache.org/confluence/display/Hive/HowToContribute) the fixVersion should be set only when the issue is resolved/closed.
> Tez: disable auto-reducer parallelism when CUSTOM_EDGE is in place
> ------------------------------------------------------------------
>
> Key: HIVE-14246
> URL: https://issues.apache.org/jira/browse/HIVE-14246
> Project: Hive
> Issue Type: Bug
> Components: Tez
> Affects Versions: 2.2.0
> Reporter: Gopal Vijayaraghavan
> Assignee: Gopal Vijayaraghavan
> Priority: Minor
> Attachments: HIVE-14246.1.patch
>
>
> The CUSTOM_SIMPLE_EDGE impl has differences between the size constraints of either edge which cannot be represented by the ShuffleVertexManager presently.
> Reducing the width based on the hashtable build side vs the streaming probe side have different consequences since there is no order of runtime between them.
> Until the two parent vertices of the shuffle hash-join are related, this feature causes massive inconsistency of performance across runs.
> For inner & semi joins, the hashtable side should have a higher priority than the streaming side and for left outer joins, the streaming side can over-take the hashtable side, being the more dominant factor in the final row-counts.
> Until such priorities can be bubbled up into ShuffleVertexManager, this feature can be disabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)