[jira] [Resolved] (HBASE-6009) Changes for HBASE-5209 are technically incompatible

["Jonathan Hsieh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hsieh resolved HBASE-6009.
-----------------------------------

      Resolution: Won't Fix
        Assignee: David S. Wang
    Release Note: HBASE-5209 was introduced in 0.92.1 and 0.94.0 but introduced an incompatibility from a 0.92.0 client.  Since this had maded it into two releases already, we've decided to leave it in.
    Hadoop Flags: Incompatible change,Reviewed  (was: Incompatible change)

It seems like from discussion and inaction, we've decided to keep this in the acknowledge the incompatiblity between 0.92.0 and 0.92.1+ series, and keep this in 0.94.0 series allowing for compatibility between 0.92.1+ and 0.94.0
                
> Changes for HBASE-5209 are technically incompatible
> ---------------------------------------------------
>
>                 Key: HBASE-6009
>                 URL: https://issues.apache.org/jira/browse/HBASE-6009
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.92.1, 0.94.0
>            Reporter: David S. Wang
>            Assignee: David S. Wang
>
> The additions to add backup masters to ClusterStatus are technically incompatible between clients and servers.  Older clients will basically not read the extra bits that the newer server pushes for the backup masters, thus screwing up the serialization for the next blob in the pipe.
> For the Writable, we can add a total size field for ClusterStatus at the beginning, or we can have start and end markers.  I can make a patch for either approach; interested in whatever folks have to suggest.  Would be good to get this in soon to limit the damage to 0.92.1 (don't know if we can get this in in time for 0.94.0).
> Either change will make us forward-compatible starting with when the change goes in, but will not fix the backwards incompatibility, which we will have to mark with a release note as there have already been releases with this change.
> Hopefully we can do this in a cleaner way when wire compat rolls around in 0.96.

--
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