[
https://issues.apache.org/jira/browse/HBASE-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583673#comment-13583673
]
Sergey Shelukhin commented on HBASE-7846:
-----------------------------------------
bq. resion
typo.
Could merge methods accept things as parameters instead of relying on fields?
Help should probably have full command for all/allrecurse, to make sure its
clear it is the first argument.
bq. if (info != null) if (Bytes.compareTo(info.getTableName(), tableName) == 0)
{
&&?
> 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
>
>
> 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
