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

stack updated HBASE-17442:
--------------------------
    Attachment: 0001-hbase-replication-module.patch

Here is a first cut at a replication module. Does the module and then tries to 
move one utility class. Currently not compiling because the moved class is 
needed by hbase-server.

Moving replication out of hbase-server will be an involved task. Replication is 
too tightly wound up in the hbase-server core. Replication classes are also 
exposed in hbase-client. Replication classes don't seem to do Interfaces so 
tough having implementation distinct from definition. I could spend a bit more 
time on it but as of this writing, it seems like a large undertaking.... 

I notice that you are doing a bunch of work moving the replication changes to 
go via Master [~zghaobac]. This is a great project. Maybe come back to this 
task of moving out to hbase-replication after this refactor is done? After more 
experience with Replication layout?

> 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
>             Fix For: 2.0.0
>
>         Attachments: 0001-hbase-replication-module.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.3.4#6332)

Reply via email to