[
https://issues.apache.org/jira/browse/PHOENIX-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271418#comment-16271418
]
Ethan Wang commented on PHOENIX-4406:
-------------------------------------
In the hbase, before desable a table, seems disable is a must (so that it stop
taking writes and clean up WAL etc?). From phoenix, I don't see where is
disabling request get called, is it part of DropTableRequest? (CQSI.dropTable)
If I understand right, disable/enable a table may be something like:
*Disable Table T:*
flush T
disable T
disable related view
disable related index
(disable stats?)
mark metadata as T disabled/update metadata cache
*Enable Table T:*
enable T
enable related view
enable/rebuild related index
(enable stats?)
mark metadata as T enabled/update metadata cache
Thoughts?
> 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)
