You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wellington Chevreuil (JIRA)" <ji...@apache.org> on 2018/11/09 14:35:00 UTC

[jira] [Created] (HBASE-21462) Add note for CopyTable section explained it does not perform a diff, but a full write from source to target

Wellington Chevreuil created HBASE-21462:
--------------------------------------------

             Summary: Add note for CopyTable section explained it does not perform a diff, but a full write from source to target
                 Key: HBASE-21462
                 URL: https://issues.apache.org/jira/browse/HBASE-21462
             Project: HBase
          Issue Type: Improvement
          Components: documentation
            Reporter: Wellington Chevreuil
            Assignee: Wellington Chevreuil


Performance is a common issue with CopyTable is when the key/time range for the data to be copied is large because it basically scans all rows on the specified range, in the source and perform related puts on the source. We should add extra note explaining that on the reference guide, to help users/admins understand when to choose between the different tools/approaches for syncing clusters.



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