[HIVE-20296] Improve HivePointLookupOptimizerRule to be able to extract from more sophisticated contexts

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Component/s: Logical Optimizer
• Assignee: Zoltan Haindrich
• Reporter: Zoltan Haindrich
• Created: 02/Aug/18 10:55
• Updated: 17/Nov/22 08:54
• Resolved: 11/Sep/18 11:22

Description

Currently it could handle conditions in the form:

( ( a=1 && b=1 && ... ) || (a=2 && b=2 && ...) || ... )

If there is some noise somewhere in the or like:

( x=18 || ( a=1 && b=1 && ... ) || (a=2 && b=2 && ...) || ... )

it stops processing.

https://github.com/apache/hive/blob/2cabb8da150b8fb980223fbd6c2c93b842ca3ee5/ql/src/java/org/apache/hadoop/hive/ql/optimizer/calcite/rules/HivePointLookupOptimizerRule.java#L238

HIVE-19097 right now unwinds some ors which can't be packed back; like query15
https://github.com/apache/hive/blob/2cabb8da150b8fb980223fbd6c2c93b842ca3ee5/ql/src/test/queries/clientpositive/perf/query15.q#L14

Issue Links

• is related to: HIVE-20704 Extend HivePreFilteringRule to support other functions
• is related to: HIVE-20712 HivePointLookupOptimizer should extract deep cases
• links to: reviewboard