[
https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219511#comment-13219511
]
stack commented on HBASE-4991:
------------------------------
bq. Online merge requires table needs to be disabled but deleteRegion
(deleteRange) does not require table needs to be disabled.
We've had ongoing conversation -- before your time so you are not expected to
have known about it -- on our doing an online merge. Its actually pretty
critical need. See HBASE-1621 for some history (Ignore its title where it
says table should be offline -- it should be online).
FYI, the current merge code is broke and unused. It works for a unit test but
I'd say its years since anyone tried to use it to actually do anything useful.
So, we are agreed that conceptually, whats going on here is region merging? If
so, that helps understanding around whats going on here. We should also likely
rename what this issue does to be about merging since thats how we've been
describing this operation over the years.
> 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
