You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Zoltan Haindrich (Jira)" <ji...@apache.org> on 2020/11/13 10:13:00 UTC
[jira] [Resolved] (HIVE-24357) Exchange SWO table/algorithm
strategy
[ https://issues.apache.org/jira/browse/HIVE-24357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltan Haindrich resolved HIVE-24357.
-------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
merged into master. Thank you Jesus for reviewing the changes!
> Exchange SWO table/algorithm strategy
> -------------------------------------
>
> Key: HIVE-24357
> URL: https://issues.apache.org/jira/browse/HIVE-24357
> Project: Hive
> Issue Type: Improvement
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: swo.before.jointree.dot.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> SWO right now runs like:
> {code}
> for every strategy s: for every table t: try s for t
> {code}
> this results in that an earlier startegy may create a more entangled operator tree behind - in case its able to merge for a less prioritized table
> it would probably make more sense to do:
> {code}
> for every table t: for every strategy s: try s for t
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)