phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4406) Add option to disable tables when dropped
Date Wed, 06 Dec 2017 17:31:00 GMT


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:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Alex Araujo
>            Priority: Critical
> Phoenix client applications can drop tables when HBase replication is actively shipping
> 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

View raw message