[
https://issues.apache.org/jira/browse/HBASE-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195507#comment-15195507
]
Andrew Purtell commented on HBASE-14866:
----------------------------------------
according to http://hbase.apache.org/book.html#hbase.versioning we guarantee
client binary compatibility (no recompliation needed) only for patch versions -
0.98.x.y or 1.x.
{quote}
Client code written to APIs available in a given patch release can run
unchanged (no recompilation needed) against the new jars of later patch
versions.
Client code written to APIs available in a given patch release might not run
against the old jars from an earlier patch version.
{quote}
> VerifyReplication should use peer configuration in peer connection
> ------------------------------------------------------------------
>
> Key: HBASE-14866
> URL: https://issues.apache.org/jira/browse/HBASE-14866
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: HBASE-14866-0.98.patch, HBASE-14866.patch,
> HBASE-14866_v1.patch, hbase-14866-branch-1-v1.patch, hbase-14866-v4.patch,
> hbase-14866-v5.patch, hbase-14866-v6.patch, hbase-14866_v2.patch,
> hbase-14866_v3.patch
>
>
> VerifyReplication uses the replication peer's configuration to construct the
> ZooKeeper quorum address for the peer connection. However, other
> configuration properties in the peer's configuration are dropped. It should
> merge all configuration properties from the {{ReplicationPeerConfig}} when
> creating the peer connection and obtaining a credentials for the peer cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
