Lots of reasons. Given the way deletes currently work, it would be extremely expensive to process multi-row deletes.
At this point there are already people questioning if we should have row/family deletes because they are expensive to process. If we move towards a new delete mechanism or optimization, see HBASE-2959 for some discussion on it, it may be feasible to have multi-row or row-range deletes but I would not expect this to be a high priority. HBase is usually used when you have to keep lots of data, not when you have lots of data churn. And typically when there is churn, it's done in a predictable way such that things like TTL can be used. I'd be interested to hear all the use cases from those looking for range deletes. Perhaps we could help you come up with some alternative strategies. I agree scanning and issuing deletes is less than ideal. JG > -----Original Message----- > From: Alexey Kovyrin [mailto:[email protected]] > Sent: Friday, September 10, 2010 11:11 AM > To: [email protected] > Subject: Re: How to delete a range of table ? > > Is there any reason this operation is not a part of the api? > > On Thu, Aug 19, 2010 at 10:47 PM, Stack <[email protected]> wrote: > > Not currently Jeff; on each next, do a delete. Could save some by > > making a deleting filter but that'd be a bit odd. > > St.Ack > > > > On Thu, Aug 19, 2010 at 6:52 PM, Jeff Zhang <[email protected]> wrote: > >> Hi all, > >> > >> I'd like to delete a range of table, but could not find a convenient > >> api. One work around is first scan the range of table and then > invoke > >> delete operation for each row. This seems not so good, is there any > >> other methods for this purpose ? > >> > >> > >> -- > >> Best Regards > >> > >> Jeff Zhang > >> > > > > > > -- > Alexey Kovyrin > http://kovyrin.net/
