[
https://issues.apache.org/jira/browse/HBASE-13216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-13216:
-----------------------------------
Fix Version/s: 0.98.13
I picked this back to 0.98 too. It's a safe compatible change. Useful as
described for identifying remaining versions that need update in a
staged/partial upgrade. While doing this I noticed we are not calculating a
source checksum in 0.98 for the version annotation. The annotation is marked
private and it's user, VersionInfo, is marked evolving, so I've added this to
0.98 as well.
> Add version info in RPC connection header
> -----------------------------------------
>
> Key: HBASE-13216
> URL: https://issues.apache.org/jira/browse/HBASE-13216
> Project: HBase
> Issue Type: Improvement
> Components: Client, rpc
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Minor
> Fix For: 2.0.0, 1.1.0, 0.98.13
>
> Attachments: 13216-v4.branch-1.txt, HBASE-13216-0.98.patch,
> HBASE-13216-v1.diff, HBASE-13216-v2.diff, HBASE-13216-v3.diff,
> HBASE-13216-v4.diff
>
>
> In the operation of a cluster, we usually want to know which clients are
> using the HBase client with critical bugs or too old version we will not
> support in future.
> By adding version info in RPC connection header, we can get these
> informations from audit log and promote them upgrade before a deadline.
> Discussions and suggestions are welcomed. Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
