[ https://issues.apache.org/jira/browse/HBASE-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Helmling updated HBASE-14866: ---------------------------------- Attachment: hbase-14866-v4.patch Attaching a new version of the patch that also merges in the fix for HBASE-14886. This has become a larger refactoring of the ZK related config methods: * config related methods have been moved from ZKUtil over to HBaseConfiguration * HBaseConfiguration.createClusterConf() should now be used wherever ZKUtil.applyClusterKeyToConf() was used before. This now unifies applying the cluster key and configuration property overrides (via key prefix) to a configuration. * HBaseConfiguration.applyClusterKeyToConf() is now private. * SyncTable now support additional target cluster config keys via the same key prefix as TableOutputFormat These moves _should_ be fine from a compatibility standpoint, as ZKUtil was annotated as private. However, the public methods added to HBaseConfiguration become part of our public stable API, so let's make sure we have them right. > 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 > > Attachments: HBASE-14866.patch, HBASE-14866_v1.patch, > hbase-14866-v4.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)