Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
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
Attachments
Attachments
Issue Links
- is blocked by
-
HIVE-24360 SharedWorkOptimizer may create incorrect plans with DPPUnion
- Closed
- is related to
-
HIVE-24365 SWO should not create complex and redundant filter expressions
- Closed
- relates to
-
HIVE-24241 Enable SharedWorkOptimizer to merge downstream operators after an optimization step
- Closed
- links to