[
https://issues.apache.org/jira/browse/PHOENIX-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6586:
---------------------------------
Description:
The salting code relies on having only a single salt value in each region.
The HBase normalizer doesn't know about this, and will merge regions for
salted tables which breaks the salted logic in Phoenix.
I propose explicitly disabling the normalizer on slated tables.
Another solution would be adding something like SplitPolicy for the normalizer,
but that requires HBase work first, and does not help with existing HBase
versions.
was:
The salting code relies on having only a single salt value in each region.
The HBase normalizer doesn't know about this, and will merge regions for salted
tables which breaks behaviour.
I proposee explicitly disableing the normalizer on slated tables.
Another solution would be adding something like SplitPolicy for the normalizer,
but that requires HBase work first, and does not help with existing HBase
versions.
> Set NORMALIZATION_ENABLED to false on salted tables
> ---------------------------------------------------
>
> Key: PHOENIX-6586
> URL: https://issues.apache.org/jira/browse/PHOENIX-6586
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 4.16.0, 5.2.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Critical
>
> The salting code relies on having only a single salt value in each region.
> The HBase normalizer doesn't know about this, and will merge regions for
> salted tables which breaks the salted logic in Phoenix.
> I propose explicitly disabling the normalizer on slated tables.
> Another solution would be adding something like SplitPolicy for the
> normalizer, but that requires HBase work first, and does not help with
> existing HBase versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
