Known Issues in Apache Phoenix
Learn about the known issues in Phoenix, the impact or changes to the functionality, and the workaround.
Technical Service Bulletins
- TSB 2022-568: HBase normalizer must be disabled for Salted Phoenix tables
- When Apache Phoenix (“Phoenix”) creates a salted table, it pre-splits the table according
to the number of salt regions. These regions must always be kept separate, otherwise Phoenix
does not work correctly.
The HBase normalizer is not aware of this requirement, and in some cases the pre-split regions are merged automatically. This causes failure in Phoenix.
The same requirement applies when merging regions of salted tables manually: regions containing different salt keys (the first byte of the rowkey) must never be merged.
Note that either automatic or manual splitting of the regions for a salted table does not cause a problem. The problem only occurs when adjacent regions containing different salt keys are merged.
- Upstream JIRA
- PHOENIX-4906
- Knowledge article
- For the latest update on this issue, see the corresponding Knowledge article: TSB 2022-568: Hbase normalizer must be disabled for Salted Phoenix tables
