[
https://issues.apache.org/jira/browse/HBASE-20148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20148:
------------------------------
Hadoop Flags: Incompatible change,Reviewed (was: Reviewed)
Release Note: A new method setSerial has been added to the interface
ReplicationPeerConfigBuilder which is marked as IA.Public. This interface is
not supposed to be implemented by client code, but if you do, this will be an
incompatible change as you need to add this method to your implementation too.
> Make serial replication as a option for a peer instead of a table
> -----------------------------------------------------------------
>
> Key: HBASE-20148
> URL: https://issues.apache.org/jira/browse/HBASE-20148
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20148-v1.patch, HBASE-20148-v2.patch,
> HBASE-20148-v3.patch, HBASE-20148.patch
>
>
> Discussed with [~zghaobac] and [~openinx] offline, HBASE-20147 can only be
> solved by adding new stages when creating a new replication peer. It will
> also effect he processing even if you do not have any table with serial
> replication. And also, the new logic introduced in ReplicationSource related
> classes will also be executed even if you do not have serial replication
> tables.
> So, we think that it maybe a better choice to move the option to
> ReplicationPeerConfig. Since if there is one table in the peer requires
> serial replication, then all the tables in this peer will be automatically
> 'serial' since the wal for these tables are mixed with the one which requires
> serial replication.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)