phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajeshbabu Chintaguntla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4360) Prevent System.Catalog from splitting
Date Thu, 01 Mar 2018 09:09:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajeshbabu Chintaguntla updated PHOENIX-4360:
---------------------------------------------
    Attachment: PHOENIX-4360_5.x-HBase-2.0.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, 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)

Mime
View raw message