[
https://issues.apache.org/jira/browse/PHOENIX-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280549#comment-16280549
]
James Taylor commented on PHOENIX-4406:
---------------------------------------
FWIW, we have a column defined in the SYSTEM.CATALOG named INDEX_STATE that we
could use for this purpose (i.e. disabling at the Phoenix layer). Part of this
JIRA could be to rename that column to something not specific to indexing
(STATUS perhaps). We still need to decide if disabling a table through Phoenix
is simply a passthrough to disabling the table in HBase or something purely at
the Phoenix layer (or both).
> 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
> 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)
