hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11393) Replication TableCfs should be a PB object rather than a string
Date Tue, 03 Nov 2015 20:08:27 GMT

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

Enis Soztutar commented on HBASE-11393:

Now, thinking more about it, I think we should do a couple of more changes to the client-visible
API. First, the String based configuration for table cfs should completely be deprecated.
Second, I think we should unify the ReplicationPeerConfiguration and table-cf configuration
so that the table CF's to filter goes inside the ReplicationPeerConfiguration. Wdyt? 

These are the functions to be deprecated at least:  
getPeerTableCFs(String id)
appendPeerTableCFs(String id, String tableCfs)
removePeerTableCFs(String id, String tableCf)

> Replication TableCfs should be a PB object rather than a string
> ---------------------------------------------------------------
>                 Key: HBASE-11393
>                 URL: https://issues.apache.org/jira/browse/HBASE-11393
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>             Fix For: 2.0.0
>         Attachments: HBASE-11393.patch, HBASE-11393_v1.patch, HBASE-11393_v2.patch, HBASE-11393_v3.patch,
HBASE-11393_v4.patch, HBASE-11393_v5.patch, HBASE-11393_v6.patch, HBASE-11393_v7.patch
> We concatenate the list of tables and column families in format  "table1:cf1,cf2;table2:cfA,cfB"
in zookeeper for table-cf to replication peer mapping. 
> This results in ugly parsing code. We should do this a PB object. 

This message was sent by Atlassian JIRA

View raw message