hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14123) HBase Backup/Restore Phase 2
Date Wed, 08 Feb 2017 20:09:41 GMT

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

Enis Soztutar commented on HBASE-14123:

bq. What kind of writeup do you expect, Enis Soztutar
We are proposing a *partial* merge of a large amount of work which is still going on. The
code comes from the branch, and it may or may not have diverged from the code in there. So,
what we need is to have a summary of the "proposal". The audience is not me, it is the whole
HBase community. There are tens of developers which may or may not be familiar with this work.
It does not have to be long but assume that whoever reads it will not be familiar with any
of this. 

Basically, you should cover what are we proposing to the HBase community: 
 - Include a short summary of the work.
 - Is this useful after merge even without remaining work fixed. 
 - Any recent changes that 
 - Include a full list of jiras in the patch (or a jira search, etc). Mark every jira with
a label if you want. 
 - How is the status of the code regards to the branch.
 - What are the remaining work items. Where are they tracked, what kind of timelines we can
expect. Do we want everything to be in 2.0, etc. 
 - How are we gonna track remaining work. Probably, we would need a distinction from "must
haves" to "good to haves". Must have jiras should be blockers.
 - What will happen to the branch, and non-merged commits there?
 - What would be compatibility guarantees once it is released. 
 - Whether we want backups to be GA in 2.0 or not. 

So, basically a proposal for the merge intended for the general hbase community. Once we have
the write up, then we can start the DISCUSS and/or VOTE threads in the dev mailing list. 

[~saint.ack@gmail.com] last time you had some concerns that your review comments were not
addressed. Can you please spend some time with this once again before we start the vote. Thanks.

> HBase Backup/Restore Phase 2
> ----------------------------
>                 Key: HBASE-14123
>                 URL: https://issues.apache.org/jira/browse/HBASE-14123
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>            Priority: Blocker
>             Fix For: 2.0.0
>         Attachments: 14123-master.v14.txt, 14123-master.v15.txt, 14123-master.v16.txt,
14123-master.v17.txt, 14123-master.v18.txt, 14123-master.v19.txt, 14123-master.v20.txt, 14123-master.v21.txt,
14123-master.v24.txt, 14123-master.v25.txt, 14123-master.v27.txt, 14123-master.v28.txt, 14123-master.v29.full.txt,
14123-master.v2.txt, 14123-master.v30.txt, 14123-master.v31.txt, 14123-master.v32.txt, 14123-master.v33.txt,
14123-master.v34.txt, 14123-master.v35.txt, 14123-master.v36.txt, 14123-master.v37.txt, 14123-master.v38.txt,
14123.master.v39.patch, 14123-master.v3.txt, 14123.master.v40.patch, 14123.master.v41.patch,
14123.master.v42.patch, 14123.master.v44.patch, 14123.master.v45.patch, 14123.master.v46.patch,
14123.master.v48.patch, 14123.master.v49.patch, 14123.master.v50.patch, 14123.master.v51.patch,
14123.master.v52.patch, 14123.master.v54.patch, 14123.master.v56.patch, 14123.master.v57.patch,
14123-master.v5.txt, 14123-master.v6.txt, 14123-master.v7.txt, 14123-master.v8.txt, 14123-master.v9.txt,
14123-v14.txt, HBASE-14123-for-7912-v1.patch, HBASE-14123-for-7912-v6.patch, HBASE-14123-v10.patch,
HBASE-14123-v11.patch, HBASE-14123-v12.patch, HBASE-14123-v13.patch, HBASE-14123-v15.patch,
HBASE-14123-v16.patch, HBASE-14123-v1.patch, HBASE-14123-v2.patch, HBASE-14123-v3.patch, HBASE-14123-v4.patch,
HBASE-14123-v5.patch, HBASE-14123-v6.patch, HBASE-14123-v7.patch, HBASE-14123-v9.patch
> Phase 2 umbrella JIRA. See HBASE-7912 for design document and description. 

This message was sent by Atlassian JIRA

View raw message