[
https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219686#comment-13219686
]
stack commented on HBASE-4991:
------------------------------
Looking at the patch again, yeah, we should expose deleteRegion apis, but it
should all run on a merge engine, not this specialization on merge, a 'delete
region engine'
Looking at the design:
+ What do we have the regionserver do anything but close of the region? Why do
we delegate to it the deletion? Why not have it done by the master? Or a
client script? Have it remove the region from .META. and from the fs? And
bridge the hole in .META.? Isn't that less complicated?
> 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
