Maryann Xue created PHOENIX-2814:
------------------------------------
Summary: WhereOptimizer does not handle multi-tenant local index
correctly when connection is non-tenant-specific
Key: PHOENIX-2814
URL: https://issues.apache.org/jira/browse/PHOENIX-2814
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.7.0
Reporter: Maryann Xue
Priority: Minor
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()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
