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

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on HBASE-21462:
--------------------------------

Results for branch master
	[build #1230 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1230/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/1230//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1230//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1230//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> 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
>    Affects Versions: 3.0.0, 2.1.5
>            Reporter: Wellington Chevreuil
>            Assignee: Wellington Chevreuil
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: HBASE-21462-master.002.patch, HBASE-21462.master.001.patch
>
>
> 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.14#76016)