[
https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257942#comment-16257942
]
Lars Hofhansl commented on PHOENIX-4360:
----------------------------------------
Then again. Perhaps it's better to keep the custom split policy class, even
when it does exactly the same as DisabledRegionSplitPolicy, that way it is
explicit that Phoenix has its own and we'll later change it again to be less
restrictive with PHOENIX-3534.
So I submit the attached patch.
> 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
>
> Attachments: 4360.txt
>
>
> 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
(v6.4.14#64029)
