phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Araujo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4406) Add option to disable tables when dropped
Date Thu, 07 Dec 2017 17:11:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282174#comment-16282174
] 

Alex Araujo commented on PHOENIX-4406:
--------------------------------------

Adding DISABLE/ENABLE syntax ties into HBase semantics nicely. The disadvantage is that end
users have to roll out a DROP in two steps (DISABLE then a DROP). Another option could be
to only rollout the DISABLE command and have a cleanup job do the rest.
It would still be good to have an option to disallow DROP commands for tables that have not
been disabled to avoid replication issues.

> Add option to disable tables when dropped
> -----------------------------------------
>
>                 Key: PHOENIX-4406
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4406
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Alex Araujo
>            Assignee: Ethan Wang
>            Priority: Critical
>
> Phoenix client applications can drop tables when HBase replication is actively shipping
edits.
> Add an option to disable the table in Phoenix's metadata when a DROP TABLE is issued.
> This will allow the HBase table to be dropped by admin actions when it's safe to do so.



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

Mime
View raw message