[PHOENIX-6402] Allow using local indexes with uncovered columns in the WHERE clause

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 5.1.1, 4.16.1, 5.2.0
• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 03/Mar/21 20:00
• Updated: 10/Mar/21 03:57
• Resolved: 10/Mar/21 00:49

Description

In PHOENIX-6400 I had to disable using local index when uncovered columns are referenced in the WHERE clause.

There are two problems:

1. The uncovered columns are represented as ProjectedColumnExpression and not correctly added as filters by the WhereCompiler
2. The scanner produced in RegionScannerFactory.getWrappedScanner does not handle this correctly.

kozdemir and I brainstormed this today.

What should happen is this:

• Do not add uncovered column expression as filters for local indexes (they would not be evaluated at right time)
• Pass the extra filter expression via a scan attribute
• Do something similar to what we do with conditional expressions (see PhoenixIndexBuilder.executeAtomicOp), where we assemble the complete tuple, then run the filter expression over it.

This would probably require some surgery, so filing it here as an Improvement in case someone signs up for it

Issue Links

• Blocked: PHOENIX-6400 Do no use local index with uncovered columns in the WHERE clause.
• links to: GitHub Pull Request #1159