[jira] [Updated] (HBASE-7158) Allow CopyTable to identify the source cluster (for replication scenarios)

2012-12-14 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-7158: - Fix Version/s: 0.94.4 0.96.0 > Allow CopyTable to identify the source clus

[jira] [Updated] (HBASE-7158) Allow CopyTable to identify the source cluster (for replication scenarios)

2012-12-14 Thread Jean-Daniel Cryans (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans updated HBASE-7158: -- Attachment: HBASE-7158-0.94-v1.patch Something like this boss? I tried to come up with

[jira] [Updated] (HBASE-7158) Allow CopyTable to identify the source cluster (for replication scenarios)

2012-11-13 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-7158: - Comment: was deleted (was: When I worked on HBASE-2195 I added a mechanism for an edit to identif

[jira] [Updated] (HBASE-7158) Allow CopyTable to identify the source cluster (for replication scenarios)

2012-11-13 Thread Lars Hofhansl (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-7158: - Description: When I worked on HBASE-2195 I added a mechanism for an edit to identify its source