[PHOENIX-2814] WhereOptimizer does not handle multi-tenant local index correctly when connection is non-tenant-specific

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.7.0
• Fix Version/s: 4.8.0
• Assignee: rajeshbabu
• Reporter: Wei Xue
• Created: 31/Mar/16 03:10
• Updated: 11/Aug/16 08:28
• Resolved: 09/Jun/16 17:41

Description

For example, if we have a multi-tenant table "A" with columns: tenant_id, id, col0, col1, PK as (tenant_id, id)
A local index table IDX_A created on A(col0) including col1.

Then if we try to use IDX_A for query "select * from A where tenant_id = '10' and col0 < 20", WhereOptimizer will compile this into a wrong ScanRanges object since _INDEX_ID column comes after TENANT_ID and using the PK start position approach just won't address this case properly. See WhereOptimizer.KeyExpressionVisitor.andKeySlots().

Issue Links

• duplicates: PHOENIX-2276 Creating index on a global view on a multi-tenant table fails with NPE