[jira] [Created] (CRUNCH-684) [crunch-hbase] HbaseTarget getting ignored even if configuration is different

["Keerthi Yanda (JIRA)" <ji...@apache.org>]

Keerthi Yanda created CRUNCH-684:
------------------------------------

             Summary: [crunch-hbase] HbaseTarget getting ignored even if configuration is different
                 Key: CRUNCH-684
                 URL: https://issues.apache.org/jira/browse/CRUNCH-684
             Project: Crunch
          Issue Type: Improvement
            Reporter: Keerthi Yanda


*Current Scenario*

* We are trying to perform put operations for a table on different clusters with the same table name. Below is the code that we are using to perform write operation:
{code:java}
pipeline.write(PCollection<Put>, HbaseTarget, WriteMode.APPEND)
{code}
* Pipeline adds this target instance to "appendedTargets" and "outputTargets" instances (which are HashSets)

*Issue:*
* As HbaseTarget's hashCode() and equals() methods are only checking for tableName, HbaseTarget with different configuration properties is getting ignored while adding it to appendedTargets/outputTargets.

*Proposal*
* Do we need to consider both tableName and atleast "hbase.zookeeper.quorum" property from "extraConf" to identify if the table(or hbaseTarget) is unique or not?
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)