hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7055) port HBASE-6371 tier-based compaction from 0.89-fb to trunk
Date Tue, 30 Oct 2012 21:32:13 GMT

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

Ted Yu commented on HBASE-7055:
-------------------------------

I read http://hbase.apache.org/book.html#decisions
There was no mentioning of forward ports, forward port from 0.89-fb branch in this particular
case.
Here is record from 0.89-fb branch w.r.t. HBASE-6371:
{code}
Differential Revision: https://phabricator.fb.com/D552051
------------------------------------------------------------------------
r1378348 | mbautin | 2012-08-28 14:13:38 -0700 (Tue, 28 Aug 2012) | 15 lines

[HBASE-6371] Level Based Compaction

Author: liyintang

Summary: We've already discussed all features here. We'll fill in a detailed summary later.

Test Plan: New tests added for size based levelAssignment. Also tests for Recent first level
traversal and vice versa.

Reviewers: liyintang, kannan

Reviewed By: liyintang

CC: hbase-eng@, mbautin
{code}
We can see Liyin reviewed the patch there.

I agree with adding document.
I want to understand how this category of forward ports should be handled.
                
> port HBASE-6371 tier-based compaction from 0.89-fb to trunk
> -----------------------------------------------------------
>
>                 Key: HBASE-7055
>                 URL: https://issues.apache.org/jira/browse/HBASE-7055
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 0.96.0
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HBASE-6371-squashed.patch, HBASE-6371-v2-squashed.patch
>
>
> There's divergence in the code :(
> See HBASE-6371 for details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message