[
https://issues.apache.org/jira/browse/HBASE-17614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137703#comment-16137703
]
Mike Drob commented on HBASE-17614:
-----------------------------------
bq. Mike Drob, you all-clear now? Or should I still tread lightly on branch-2
to avoid smacking you?
Nah, do whatever. Master you'll want parent to be {{hbase-build-configuration}}
and branch-2 you'll want {{hbase}}, but you will need to adjust for version in
the pom.xml anyway, so it's not like you were getting a clean backport. If
error-prone ends up getting backported to branch-2 (I keep waffling back and
forth on this) then I'll deal with the conflicts then, you shouldn't have to
worry about making less work for me at this point.
> Move Backup/Restore into separate module
> -----------------------------------------
>
> Key: HBASE-17614
> URL: https://issues.apache.org/jira/browse/HBASE-17614
> Project: HBase
> Issue Type: Task
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Blocker
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBASE-17614-v1.patch, HBASE-17614-v2.patch,
> HBASE-17614-v3.patch, HBASE-17614-v4.patch, HBASE-17614-v5.patch
>
>
> Move all the backup code into separate hbase-backup module.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
