[
https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210098#comment-13210098
]
Lars Hofhansl commented on HBASE-4991:
--------------------------------------
I had thought of something similar in HBASE-5268, but it turns out that is not
so simple. Maybe a range delete marker is easier to implement as the beginning
is a known point; still how would a scan know what deleted markers would be in
effect?
We'd have to store all range delete markers at the beginning of the file, and
then seek there on every scan. There's there question about when it is safe to
collect the range marker, etc.
I agree with Todd on the API as well. At the same time I agree with Ted & co.
Being able to delete an entire region is powerful (especially with pluggable
RegionSplitPolicies - HBASE-5304).
So generally I'd prefer an implementation that either enforces start-range and
end-range to coincide with the a region (although that is awkward), or have
logic that splits the two adjacent regions and deletes the whole range by
removing a range of regions (including the newly created partial regions).
> 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
