You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Keerthi Yanda (JIRA)" <ji...@apache.org> on 2019/05/01 18:15:00 UTC

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

    [ https://issues.apache.org/jira/browse/CRUNCH-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831154#comment-16831154 ] 

Keerthi Yanda edited comment on CRUNCH-684 at 5/1/19 6:15 PM:
--------------------------------------------------------------

Thank you [~noslowerdna].

We verified, by makes changes locally in one of our services. And verified count(18080) on both AWS and on-prem clusters.

 


was (Author: keerthiyanda):
Thank you [~noslowerdna]. 

We verified, by makes changes locally in one of our services ([programs-service|https://github.cerner.com/KY046557/programs-services/commit/33a6935b55dc4876453178b2b1870b931f22175b#diff-c2b014be3918917bb9332b89e49f9b55R22]).

Attaching the screenshots showing the number of records in both shiva and metroid clusters.
*Shiva:*
  !Shiva.png! 
*Metroid:*
 !Metroid.png! 


> [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
>            Priority: Minor
>
> *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 "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)