[
https://issues.apache.org/jira/browse/HBASE-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-8202:
--------------------------
Summary: MultiTableOutputFormat should support writing to another HBase
cluster (was: MultiTableOutputFormat should support hbase.mapred.output.quorum)
> MultiTableOutputFormat should support writing to another HBase cluster
> ----------------------------------------------------------------------
>
> Key: HBASE-8202
> URL: https://issues.apache.org/jira/browse/HBASE-8202
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Ted Yu
>
> This was brought up by David Koch in thread 'hbase.mapred.output.quorum
> ignored in Mapper job with HDFS source and HBase sink' where he wanted to
> import a file on HDFS from one cluster A (source) into HBase
> tables on a different cluster B (destination) using a Mapper job with an
> HBase sink.
> Here is my analysis:
> MultiTableOutputFormat doesn't extend TableOutputFormat:
> {code}
> public class MultiTableOutputFormat extends
> OutputFormat<ImmutableBytesWritable, Mutation> {
> {code}
> Relevant configuration w.r.t. output quorum is setup in
> TableOutputFormat#setConf():
> {code}
> public void setConf(Configuration otherConf) {
> this.conf = HBaseConfiguration.create(otherConf);
> String tableName = this.conf.get(OUTPUT_TABLE);
> if(tableName == null || tableName.length() <= 0) {
> throw new IllegalArgumentException("Must specify table name");
> }
> String address = this.conf.get(QUORUM_ADDRESS);
> int zkClientPort = conf.getInt(QUORUM_PORT, 0);
> String serverClass = this.conf.get(REGION_SERVER_CLASS);
> String serverImpl = this.conf.get(REGION_SERVER_IMPL);
> try {
> if (address != null) {
> ZKUtil.applyClusterKeyToConf(this.conf, address);
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
