[
https://issues.apache.org/jira/browse/HBASE-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Marc Spaggiari updated HBASE-7846:
---------------------------------------
Attachment: HBASE-7846-v2-trunk.patch
Hi Sergey,
Thanks a lot for the review!
I'm not sure to get the comment about the parameters. run() is from the
interface and is called from the main. In the run() we are parsing the
parameters from parseArgs which is getting the table name, regions, and other
paramters if any and then directly running the merge. Can you please suggest a
way? I'm not sure to get it.
I fixed the other suggestions. Not 100% sure about the best way to display the
usage.
> 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
