hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guanghao Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17442) Move most of the replication related classes to hbase-server package
Date Wed, 09 Aug 2017 03:35:01 GMT

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

Guanghao Zhang commented on HBASE-17442:
----------------------------------------

bq. Do we expect users to move to latest branch-1 release before upgrading to 2.0 ?
bq. I think the answer has to be no.
So if we want remove a public method in 2.0, it need to be marked as deprecated in all 1.*
branches? Or it only to be marked in the latest branch-1?


> 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
>
>         Attachments: 0001-hbase-replication-module.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)

Mime
View raw message