[PHOENIX-6587] Handle explicit pre-splits for new salted tables and validate splits when creating salted tables on existing HBase tables

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Do
• Affects Version/s: 5.2.0
• Component/s: core
• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 04/Nov/21 07:41
• Updated: 24/May/23 13:05
• Resolved: 24/May/23 13:05

Description

Specifying the split points manually on salted tables can break them.
The easiest thing to do is to disallow it, which ensures that the table is created with the default per bucket presplit.

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-6616 Alter table command can be used to set normalization_enabled=true on salted tables
• is superceded by: PHOENIX-6910 Scans created during query compilation and execution against salted tables need to be more resilient
• relates to: PHOENIX-6673 Local indexing broken by manually splitting table at arbitrary point
• links to: GitHub Pull Request #1353