[
https://issues.apache.org/jira/browse/PHOENIX-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282662#comment-16282662
]
Vincent Poon commented on PHOENIX-4442:
---------------------------------------
If we have HBASE-12091 , then I don't think having a column is as important. I
think the original motivation for this feature was to have a column value
represent a table being disabled at the Phoenix level, but still be active at
the HBase level. That way queued replication edits could continue to drain at
the HBase level on the destination, after which the table could be dropped.
With HBASE-12091, the queued replication edits don't matter anymore if the
table is dropped on the destination.
If we don't want to wait for HBASE-12091 and need something now, then I say we
just add a new column. The existing INDEX_STATE relies on some delicate state
transitions and we made a lot of improvements to ensure the state is always
correct. Adding in new states would potentially throw a monkey wrench into all
of that.
> Rename system catalog INDEX_STATE to STATE
> ------------------------------------------
>
> Key: PHOENIX-4442
> URL: https://issues.apache.org/jira/browse/PHOENIX-4442
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Ethan Wang
>
> Rename system catalog INDEX_STATE to STATE so that this column can be used
> for table as well
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
