[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-20 Thread Duo Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang updated HBASE-19492:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed the addendum to master and branch-2 so that I can land my work on branch 
HBASE-19397.

Thanks [~zghaobac] for reviewing.

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch, 
> HBASE-19492.master.004.patch, HBASE-19492.master.005.patch, 
> HBASE-19492.master.addendum.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-20 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Status: Patch Available  (was: Reopened)

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch, 
> HBASE-19492.master.004.patch, HBASE-19492.master.005.patch, 
> HBASE-19492.master.addendum.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-20 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Attachment: HBASE-19492.master.addendum.patch

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch, 
> HBASE-19492.master.004.patch, HBASE-19492.master.005.patch, 
> HBASE-19492.master.addendum.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-19 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
  Resolution: Fixed
Hadoop Flags: Incompatible change,Reviewed
  Status: Resolved  (was: Patch Available)

Pushed to master and branch-2.

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch, 
> HBASE-19492.master.004.patch, HBASE-19492.master.005.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-19 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Release Note: 
Add two new field:  EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS to replication peer 
config.

If replicate_all flag is true, it means all user tables will be replicated to 
peer cluster. Then allow config exclude namespaces or exclude table-cfs which 
can't be replicated to  peer cluster.

If replicate_all flag is false, it means all user tables can't be replicated to 
peer cluster. Then allow to config namespaces or table-cfs which will be 
replicated to peer cluster.

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch, 
> HBASE-19492.master.004.patch, HBASE-19492.master.005.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-18 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Attachment: HBASE-19492.master.005.patch

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch, 
> HBASE-19492.master.004.patch, HBASE-19492.master.005.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-18 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Attachment: HBASE-19492.master.004.patch

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch, 
> HBASE-19492.master.004.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-18 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Fix Version/s: 2.0.0-beta-1

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-13 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Attachment: HBASE-19492.master.003.patch

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.003.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-12 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Attachment: HBASE-19492.master.002.patch

Retry.

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch, 
> HBASE-19492.master.002.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-12 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Attachment: HBASE-19492.master.002.patch

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch, HBASE-19492.master.002.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-11 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Attachment: HBASE-19492.master.002.patch

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19492.master.001.patch, 
> HBASE-19492.master.002.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-11 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Status: Patch Available  (was: Open)

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19492.master.001.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

2017-12-11 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-19492:
---
Attachment: HBASE-19492.master.001.patch

> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -
>
> Key: HBASE-19492
> URL: https://issues.apache.org/jira/browse/HBASE-19492
> Project: HBase
>  Issue Type: Improvement
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19492.master.001.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in 
> HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. 
> And on our cluster we have more config: EXCLUDE_NAMESPACE and 
> EXCLUDE_TABLECFS for replication peer. Let me tell more about our use case. 
> We have two online serve cluster and one offline cluster for MR/Spark job. 
> For online cluster, all tables will replicate to each other. And not all 
> tables will replicate to offline cluster, because not all tables need OLAP 
> job. We have hundreds of tables and if only one table don't need replicate to 
> offline cluster, then you will config a lot of tables in replication peer 
> config. So we add a new config option is EXCLUDE_TABLECFS. Then you only need 
> config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or 
> TABLECFS means which namespace/tables need replicate to peer cluster. When 
> replicate_all flag is true, you can config EXCLUDE_NAMESPACE or 
> EXCLUDE_TABLECFS means which namespace/tables can't replicate to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)