[
https://issues.apache.org/jira/browse/HBASE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446442#comment-13446442
]
Gregory Chanan commented on HBASE-6268:
---------------------------------------
Brought up on dev list under the title "0.92/0.94 compatibility and
HBASE-5206." My issue is more with leaving in HBASE-5206 as is in 0.94.2 -- I
probably should have posted on that JIRA. Sorry about that.
My reading of this patch is that it will work whether we leave in HBASE-5206 or
we do the change I propose on the e-mail (moving the enabled state to a
different znode). Do you agree, Ted/Lars?
One nit about the patch, the comment on the isEnabledTable function is no
longer valid:
{code}
* Go to zookeeper and see if state of table is {@link TableState#ENABLED}.
{code}
but the state doesn't have to be enabled, it can also be null (and should
probably point to this JIRA to explain why both are valid?).
> Can't enable a table on a 0.94 cluster from a 0.92 client
> ---------------------------------------------------------
>
> Key: HBASE-6268
> URL: https://issues.apache.org/jira/browse/HBASE-6268
> Project: HBase
> Issue Type: Bug
> Reporter: Jean-Daniel Cryans
> Assignee: Ted Yu
> Fix For: 0.92.2
>
> Attachments: 6268-92.txt
>
>
> In 0.92 we know a table's enabled by doing this in HCM.isEnabledTable:
> bq. return getTableState(zkw, tableName) == null;
> In 0.94 we do:
> bq. return getTableState(zkw, tableName) == TableState.ENABLED;
> So what happens is that the the 0.92 client will hang forever since the znode
> contains ENABLED instead of being absent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
