[HIVE-24357] Exchange SWO table/algorithm strategy

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0
• Labels: pull-request-available
• Assignee: Zoltan Haindrich
• Reporter: Zoltan Haindrich
• Created: 04/Nov/20 14:12
• Updated: 13/Nov/20 10:24
• Resolved: 13/Nov/20 10:12

Description

SWO right now runs like:

for every strategy s: for every table t: try s for t

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:

for every table t: for every strategy s: try s for t

Issue Links

• is blocked by: HIVE-24360 SharedWorkOptimizer may create incorrect plans with DPPUnion
• is related to: HIVE-24365 SWO should not create complex and redundant filter expressions
• relates to: HIVE-24241 Enable SharedWorkOptimizer to merge downstream operators after an optimization step
• links to: GitHub Pull Request #1653
• links to: j