[IMPALA-8834] Investigate enabling safe version of OPTIMIZE_PARTITION_KEY_SCANS by default

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 4.0.0
• Component/s: Backend
• Labels: perf
• Target Version: Product Backlog
• Epic Color: ghx-label-1
• Assignee: Tim Armstrong
• Reporter: Tim Armstrong
• Created: 05/Aug/19 21:37
• Updated: 27/Mar/23 23:01
• Resolved: 21/May/20 03:30

Description

Just an idea I had while updating the docs. We already have the logic in the planner to determine when a partition key scan has "distinct" semantics - i.e. you obtain the correct results so long as the scan returns 0 rows for a partition when there are no rows present, and at least one row when there is a row present (but the exact number doesn't affect correctness).

We could push this knowledge down into the scan nodes and have them terminate early. This would be quite efficient if file handles and footers were already cached and greatly reduce the number of rows flowing through the rest of the plan.

Issue Links

• causes: IMPALA-11081 Partition key scan optimization may return incorrect results when partition file have more than one block