[PHOENIX-6673] Local indexing broken by manually splitting table at arbitrary point

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.2.0
• Component/s: core
• Assignee: Unassigned
• Reporter: Istvan Toth
• Created: 23/Mar/22 08:05
• Updated: 15/Aug/23 06:13

Description

While working on PHOENIX-6587, I found that splitting tables with local indexes on certain points will break the local indexing code, and result in incorrect query results.

When a table is pre-split by Phoenix, or automatically split by HBase, then split points always have a minimum length that is equal to the possible minimum length of the table rowkey. 
The automatic split always happens at an existing rowkey, and SchemaUtil.processSplits() has code that approximates the same behaviour for pre-split tables.

However, it is still possible to split the table manually from HBase at points that do not satisfy the above requirement, which breaks local indexing.

Issue Links

• is related to: PHOENIX-6587 Handle explicit pre-splits for new salted tables and validate splits when creating salted tables on existing HBase tables
• relates to: PHOENIX-6684 When hbase pre-partition and Phoenix map the table，we select by local index will failed。