[
https://issues.apache.org/jira/browse/HBASE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100176#comment-16100176
]
Sean Busbey commented on HBASE-17442:
-------------------------------------
{quote}
Because we want to fix this in hbase 2.0, I thought we should mark it as
deprecated in branch-1. Let me prepare a patch for branch-1.
{quote}
Deprecating in latest branch-1 will be nice as advance warning to downstream
users, but isn't sufficient for breaking a IA.Public/Stable API. We claim we
will deprecate such APIs "for a major version" which would mean they'd need to
be marked in 1.0 to be broken in 2.0+. We could, of course, revisit this stance
now that we've had so much time to see its impact in branch-1. I'm also not
sure how well we've stuck to our promises to date.
{quote}
Do we expect users to move to latest branch-1 release before upgrading to 2.0 ?
{quote}
We should get a DISCUSS going on dev@ about expectations around upgrade.
Stack's "state of 2.0" document should have those who've already expressed
interest/concern around upgrades (if anyone).
I think the answer to this is no.
> 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)
