You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2017/11/09 01:05:00 UTC

[jira] [Created] (PHOENIX-4360) Prevent System.Catalog from splitting

Lars Hofhansl created PHOENIX-4360:
--------------------------------------

             Summary: 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
            Priority: Critical


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.
[~apurtell]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)