[
https://issues.apache.org/jira/browse/HBASE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133799#comment-16133799
]
Appy commented on HBASE-17442:
------------------------------
Uploaded new patch which is same as [~zghaobac]'s except that we are moving the
classes to separate hbase-replication module.
Since these classes are not needed in hbase-client, and since they don't need
anything from hbase-server, there's not point moving them to hbase-server.
Probably the best time to start hbase-replication module.
However, separating interfaces and implementations into different packages
within this module will be much more involved work (right now everything is in
o.a.h.h.replication) and something for which i don't have bandwidth.
Eventually, it'll be great if we can move out more replication pieces from
hbase-server to this module, but for now, maybe this is great start?
> Move most of the replication related classes to hbase-server package
> --------------------------------------------------------------------
>
> Key: HBASE-17442
> URL: https://issues.apache.org/jira/browse/HBASE-17442
> Project: HBase
> Issue Type: Sub-task
> Components: build, Replication
> Affects Versions: 2.0.0
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Critical
> Fix For: 2.0.0-alpha-3
>
> Attachments: 0001-hbase-replication-module.patch,
> HBASE-17442.master.001.patch, HBASE-17442.v1.patch, HBASE-17442.v2.patch,
> HBASE-17442.v2.patch, HBASE-17442.v3.patch
>
>
> After the replication requests are routed through master, replication
> implementation details didn't need be exposed to client. We should move most
> of the replication related classes to hbase-server package.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
