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

Ted Yu commented on HBASE-7158:
-------------------------------

I wonder if it was just me who got the following:
{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) 
on project hbase: Compilation failure: Compilation failure:
[ERROR] 
/Users/tyu/94-hbase/src/main/java/org/apache/hadoop/hbase/mapreduce/Import.java:[154,8]
 cannot find symbol
[ERROR] symbol  : class HConnection
[ERROR] location: class org.apache.hadoop.hbase.mapreduce.Import.Importer
[ERROR] 
/Users/tyu/94-hbase/src/main/java/org/apache/hadoop/hbase/mapreduce/Import.java:[154,33]
 cannot find symbol
[ERROR] symbol  : variable HConnectionManager
[ERROR] location: class org.apache.hadoop.hbase.mapreduce.Import.Importer
{code}
                
> Allow CopyTable to identify the source cluster (for replication scenarios)
> --------------------------------------------------------------------------
>
>                 Key: HBASE-7158
>                 URL: https://issues.apache.org/jira/browse/HBASE-7158
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.96.0, 0.94.4
>
>         Attachments: HBASE-7158-0.94-v1.patch
>
>
> When I worked on HBASE-2195 I added a mechanism for an edit to identify its 
> source cluster, so that replication would not bounce it back to the source.
> See: {{this.clusterId = 
> zkHelper.getUUIDForCluster(zkHelper.getZookeeperWatcher());}} in 
> ReplicationSource, and {{put.setClusterId(entry.getKey().getClusterId());}} 
> in ReplicationSink.
> In master-master replication scenarios, it would very useful if CopyTable 
> would identify the source cluster (by tagging each Put/Delete with the source 
> clusterId before applying it).

--
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

Reply via email to