[
https://issues.apache.org/jira/browse/HBASE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang resolved HBASE-5106.
--------------------------------
Resolution: Won't Fix
Probably it is not needed at all.
> HBASE-3065 recoverable ZooKeeper, the new metadata introduced setData call
> breaks old hbase client.
> ---------------------------------------------------------------------------------------------------
>
> Key: HBASE-5106
> URL: https://issues.apache.org/jira/browse/HBASE-5106
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0, 0.94.0
> Reporter: Jimmy Xiang
>
> Old hbase client which talks to the new hbase server could not understand the
> new metadata. We should re-think how to check setData BADVERSION error.
> How about we check the full actual data? If the actual data in ZK is what we
> want to set, then we are good. Of course, this data could be set actually by
> someone else, in this case, is it safe not to throw a KeeperException?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
