hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Krishna Dara (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14866) VerifyReplication should use peer configuration in peer connection
Date Tue, 15 Mar 2016 11:17:33 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195114#comment-15195114

Hari Krishna Dara commented on HBASE-14866:

The change from hbase.mapred.outputtable to hbase.mapred.output.outputtable breaks projects
that are built against older hbase libraries in a subtle way. Doesn't hbase ensure API compatibility
across minor version changes without having to recompile? The issue specifically is that the
projects that refer to the OUTPUT_TABLE constant may have the constant value inlined by javac,
so those projects will continue to pass in the old value for the configuration key.

> 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

View raw message