[
https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209661#comment-13209661
]
Todd Lipcon commented on HBASE-4991:
------------------------------------
Maybe I'm misunderstanding the use case, but I'm slightly skeptical that there
isn't a simpler way of solving the same thing.
It seems like this conflates two operations: 1) delete a bunch of data within a
range, and 2) merge a region back with its neighbors. #2 is a more general
"merge small regions" operation, which I think should be attacked orthogonally
to the issue of #1 (bulk range delete).
My other concern is that the API here exposes the concept of regions. A better
API would be deleteRange(startKey, endKey). It might be implemented underneath
by splitting the table such that startKey is the first key in some region, and
endKey is the last key in another, and then deleting the underlying regions.
See
http://incubator.apache.org/accumulo/user_manual_1.4-incubating/Table_Configuration.html#Delete_Range
for example
> Provide capability to delete named region
> -----------------------------------------
>
> Key: HBASE-4991
> URL: https://issues.apache.org/jira/browse/HBASE-4991
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Mubarak Seyed
> Fix For: 0.94.0
>
> Attachments: HBASE-4991.trunk.v1.patch, HBASE-4991.trunk.v2.patch
>
>
> See discussion titled 'Able to control routing to Solr shards or not' on
> lily-discuss
> User may want to quickly dispose of out of date records by deleting specific
> regions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
