You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Bharath Vissapragada (Jira)" <ji...@apache.org> on 2020/08/26 16:05:00 UTC

[jira] [Created] (HBASE-24955) Clarify patch upgrade compatibility guarantees

Bharath Vissapragada created HBASE-24955:
--------------------------------------------

             Summary: Clarify patch upgrade compatibility guarantees
                 Key: HBASE-24955
                 URL: https://issues.apache.org/jira/browse/HBASE-24955
             Project: HBase
          Issue Type: Improvement
          Components: documentation
    Affects Versions: 3.0.0-alpha-1, 2.3.3, 1.7.0
            Reporter: Bharath Vissapragada


Per the [compatibility|https://hbase.apache.org/book.html#hbase.versioning] guidelines (specifically section "Client-Server wire protocol compatibility
 ") which says "We could only allow upgrading the server first. I.e. the server would be backward compatible to an old client, that way new APIs are OK."

This gives an impression that it is fine to break API compatibility in patch upgrades and expect the users to upgrade server binaries first before upgrading clients. However, when considering a back-port of HBASE-24765, it was noted by [~zhangduo] and [~ndimiduk] that this compatibility shouldn't be broken. Seems like something that should be clarified in the docs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)