[
https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381704#comment-16381704
]
Rajeshbabu Chintaguntla commented on PHOENIX-4360:
--------------------------------------------------
Here is the patch for 5.x branch. But in HBase 2.0 able the split the region
explicitly even when shouldSplit return false. So raised HBASE-20111 to fix it.
> Prevent System.Catalog from splitting
> -------------------------------------
>
> Key: PHOENIX-4360
> URL: https://issues.apache.org/jira/browse/PHOENIX-4360
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.13.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Blocker
> Fix For: 4.14.0, 5.0.0
>
> Attachments: 4360-v2-0.98.txt, 4360-v2.txt, 4360.txt,
> PHOENIX-4360_5.x-HBase-2.0.patch
>
>
> Just talked to [~jamestaylor].
> It turns out that currently System.Catalog is not prevented from splitting
> generally, but does not allow splitting within a schema.
> In the multi-tenant case that is not good enough. When System.Catalog splits
> and a base table and view end up in different regions the following can
> happen:
> * DROP CASCADE no longer works for those views
> * Adding/removing columns to/from the base table no longer works
> Until PHOENIX-3534 is done we should simply prevent System.Catalog from
> splitting. (just like HBase:meta)
> [~apurtell]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
