[
https://issues.apache.org/jira/browse/HBASE-15370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180116#comment-15180116
]
Jonathan Hsieh commented on HBASE-15370:
----------------------------------------
Though this closed I wanted to address the questions here. Here's a rough
picture of what I was thinking the tree would look like after a successful
merge.
{code}
t# = trunk commit
b# = branch-1 commit
x# = hbase-11339 commit
y# = hbase-15370 commit.
..
b7 Life in branch-1 goes on as normal
b6 Merge into branch-1
|\
| +y5 Merge attempt after vote passes into hbase-15370
|/ |
b5 | Random branch-1 commit
b4 | Random branch-1 commit
|\ |
| +y4 Merge attempt of branch-1 into hbase-15370 (vote called)
|/ y3 (last backport of mob feature from trunk)
| y2 ..
| y1 (backport of mob feature from trunk)
. b3 |
. b2 |
| b1 |
|/ |
| |
t2 | hbase-11339 merged to trunk (trunk is no longer interesting after
this)
| \ /
| x1 (last commit of hbase-11339 before merge to trunk)
| x0
| /
t1 (last merge with trunk and hbase-11339)
..
{code}
> Backport Moderate Object Storage (MOB) to branch-1
> --------------------------------------------------
>
> Key: HBASE-15370
> URL: https://issues.apache.org/jira/browse/HBASE-15370
> Project: HBase
> Issue Type: Task
> Reporter: Ted Yu
> Fix For: 1.4.0
>
> Attachments: 15370-test.out, HBASE-15370-branch-1.v1.patch,
> HBASE-15370-branch-1.v2.patch, merge-conflict.list, mob-cmmits.txt,
> mob-commits-v2.txt
>
>
> MOB feature was integrated to master branch half a year ago.
> Since then there have been bug fixes which stabilize the feature.
> Some customers have been using it at PB scale.
> Here is discussion thread on dev mailing list:
> http://search-hadoop.com/m/YGbbDSqxD1PYXK62/hbase+MOB+in+branch-1&subj=Re+MOB+in+branch+1+Re+RESULT+VOTE+Merge+branch+hbase+11339+HBase+MOB+to+trunk+
> This issue is to backport MOB feature to branch-1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
