[
https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257478#comment-16257478
]
Lars Hofhansl edited comment on PHOENIX-4360 at 11/17/17 7:59 PM:
------------------------------------------------------------------
Here's a simple patch doing just that.
[~jamestaylor], [~apurtell], should this go into 4.13.1?
was (Author: lhofhansl):
Here's a simple patch doing just that.
[~jamestaylor], [~apurtell]
> 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)
