hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7846) Add support for merging implicit regions in Merge tool
Date Wed, 03 Jul 2013 16:22:20 GMT

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

Jimmy Xiang commented on HBASE-7846:

bq. Should we call HRegion#mergeAdjacent instead of HRegion#merge in Merge.java for the 'all'
or 'allrecurse' case ? 

By the way, there is some good feature in HMerge: merge some small regions.  Should we get
it into the merge tool?
> Add support for merging implicit regions in Merge tool
> ------------------------------------------------------
>                 Key: HBASE-7846
>                 URL: https://issues.apache.org/jira/browse/HBASE-7846
>             Project: HBase
>          Issue Type: Improvement
>          Components: util
>            Reporter: Kaufman Ng
>            Assignee: Jean-Marc Spaggiari
>            Priority: Minor
>         Attachments: HBASE-7846-v0-trunk.patch, HBASE-7846-v1-trunk.patch, HBASE-7846-v2-trunk.patch
> Currently org.apache.hadoop.hbase.util.Merge needs 2 region names to be explicitly specified
to perform a merge.  This can be cumbersome.
> One idea for improvement is to have Merge to figure out all the adjacent regions and
perform the merges.  
> For example:
> regions before merge: row-10, row-20, row-30, row-40, row-50
> regions after merge: row-10, row-30, row-50
> In the above example, region names of "row-10" and "row-20" are merged to become a new
bigger region of "row-10".

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

View raw message