[PHOENIX-6910] Scans created during query compilation and execution against salted tables need to be more resilient

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.1.3
• Fix Version/s: 5.2.0, 5.1.3
• Release Note: Queries on salted tables now work correctly even if rows belonging in different buckets are present in a single region.
• Assignee: Istvan Toth
• Reporter: Jacob Isaac
• Created: 15/Mar/23 18:01
• Updated: 24/Jul/23 08:14
• Resolved: 21/Jul/23 04:48

Description

The Scan objects created during where compilation and execution phases are incorrect when salted tables are involved and their regions have moved. 

Issue Links

• is related to: PHOENIX-4906 Introduce a coprocessor to handle cases where we can block merge for regions of salted table when it is problemetic
• is related to: PHOENIX-6952 Do not disable normalizer on salted tables
• supercedes: PHOENIX-6587 Handle explicit pre-splits for new salted tables and validate splits when creating salted tables on existing HBase tables
• links to: GitHub Pull Request #1607