You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Subrat Mishra (JIRA)" <ji...@apache.org> on 2019/05/15 06:19:00 UTC
[jira] [Assigned] (HBASE-22055) Support to compare different CF
names between source and peer clusters in VerifyReplication
[ https://issues.apache.org/jira/browse/HBASE-22055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Subrat Mishra reassigned HBASE-22055:
-------------------------------------
Assignee: Subrat Mishra (was: Toshihiro Suzuki)
> Support to compare different CF names between source and peer clusters in VerifyReplication
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-22055
> URL: https://issues.apache.org/jira/browse/HBASE-22055
> Project: HBase
> Issue Type: Improvement
> Reporter: Toshihiro Suzuki
> Assignee: Subrat Mishra
> Priority: Major
>
> After HBASE-21201 and HBASE-21871, we can compare any 2 tables in any remote clusters with specifying both peerId and --peerTableName in VerifyReplication. However, we can compare only the same CF names between source and peer clusters in the tool. So I would like to propose to allow the tool to be able to compare different CF names between source and peer clusters.
> Like CopyTable, I think we can make the tool to be able to specify column family mapping with --families like the following:
> {code}
> --families=sourceCf:peerCf,cf2,cf3
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)