[jira] [Updated] (HBASE-21462) Add note for CopyTable section explained it does not perform a diff, but a full write from source to target
[ https://issues.apache.org/jira/browse/HBASE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil updated HBASE-21462: - Affects Version/s: 3.0.0 2.1.5 > 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)
[jira] [Updated] (HBASE-21462) Add note for CopyTable section explained it does not perform a diff, but a full write from source to target
[ https://issues.apache.org/jira/browse/HBASE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil updated HBASE-21462: - Resolution: Fixed Fix Version/s: 3.0.0 Status: Resolved (was: Patch Available) > 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 >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)
[jira] [Updated] (HBASE-21462) Add note for CopyTable section explained it does not perform a diff, but a full write from source to target
[ https://issues.apache.org/jira/browse/HBASE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil updated HBASE-21462: - Attachment: HBASE-21462-master.002.patch > 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 >Priority: Minor > 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.3#76005)
[jira] [Updated] (HBASE-21462) Add note for CopyTable section explained it does not perform a diff, but a full write from source to target
[ https://issues.apache.org/jira/browse/HBASE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil updated HBASE-21462: - Status: Patch Available (was: In Progress) > 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 >Priority: Minor > 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.3#76005)
[jira] [Updated] (HBASE-21462) Add note for CopyTable section explained it does not perform a diff, but a full write from source to target
[ https://issues.apache.org/jira/browse/HBASE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil updated HBASE-21462: - Status: In Progress (was: Patch Available) > 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 >Priority: Minor > 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.3#76005)
[jira] [Updated] (HBASE-21462) Add note for CopyTable section explained it does not perform a diff, but a full write from source to target
[ https://issues.apache.org/jira/browse/HBASE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-21462: --- Status: Patch Available (was: Open) > 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 >Priority: Minor > Attachments: 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.3#76005)
[jira] [Updated] (HBASE-21462) Add note for CopyTable section explained it does not perform a diff, but a full write from source to target
[ https://issues.apache.org/jira/browse/HBASE-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil updated HBASE-21462: - Attachment: HBASE-21462.master.001.patch > 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 >Priority: Minor > Attachments: 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.3#76005)
