hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14821) CopyTable should allow overriding more config properties for peer cluster
Date Tue, 24 Nov 2015 20:30:11 GMT

     [ https://issues.apache.org/jira/browse/HBASE-14821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Gary Helmling updated HBASE-14821:
      Resolution: Fixed
    Release Note: Configuration properties for org.apache.hadoop.hbase.mapreduce.TableOutputFormat
can now be overridden by prefixing the property keys with "hbase.mapred.output.".  When the
configuration is applied to TableOutputFormat, these entries will be rewritten with the prefix
removed -- ie. "hbase.mapred.output.hbase.security.authentication" becomes "hbase.security.authentication".
 This can be useful when directing output to a peer cluster with different security configuration,
for example.
          Status: Resolved  (was: Patch Available)

Thanks for reviews [~chenheng] and [~eclark]!

Committed to master, branch-1, and branch-1.2.

> CopyTable should allow overriding more config properties for peer cluster
> -------------------------------------------------------------------------
>                 Key: HBASE-14821
>                 URL: https://issues.apache.org/jira/browse/HBASE-14821
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>         Attachments: HBASE-14821.patch
> When using CopyTable across two separate clusters, you can specify the ZK quorum for
the destination cluster, but not much else in configuration overrides.  This can be a problem
when the cluster configurations differ, such as when using security with different configurations
for server principals.
> We should provide a general way to override configuration properties for the peer / destination
cluster.  One option would be to allow use of a prefix for command line properties ("peer.property.").
 Properties matching this prefix will be stripped and merged to the peer configuration.

This message was sent by Atlassian JIRA

View raw message