RE: Some suggestions for future features

[Anoop Sam John <an...@huawei.com>]

>We've started to implement a coprocessor to move the Scan and 
Delete at RS level but, if the API above can delete also columns and not 
entire rows then it will be welcomed :)

@Daniel 
You are doing it using Endpoints?

@Dev
Can we provide a built in end point for this kind of bulk delete? We are now giving an Aggregation endpoint.
Handling this kind of scan and delete at server side itself will be giving performance boost.

I have done some basic implementation and tested for the performance advantage of this end point based delete over the normal way of scan to client and then delete.  In the local mini cluster itself it is promising!

Also in this delete we need to use the bulk delete at region level. [See  HBASE-6284]

-Anoop-
________________________________________
From: Daniel Iancu [daniel.iancu@1and1.ro]
Sent: Friday, June 08, 2012 10:17 PM
To: dev@hbase.apache.org
Cc: Andrew Purtell
Subject: Re: Some suggestions for future features

>> 3. Row prefix delete operation - Delete all rows which starts with a 'prefix'
> This is interesting.
>
> Worth considering a Delete API that takes a Scan (or equivalent*) as argument?
>
> * - Possibly pulling up the start row, stop row, filter chain fields
> of Scan into a more generic object that can be passed to such an API
> and extended by Scan, if the use of Scan in an API like Delete leads
> in consensus opinion to a mixed metaphor.


We have a use case where we need to delete columns but we don't know
their rows. We run a Scan on a range of rows and custom-filter the rows
containg the columns to be deleted. Then we delete all the columns from
the Scan result. This is a 2 step operation and it implies networks
traffic.  We've started to implement a coprocessor to move the Scan and
Delete at RS level but, if the API above can delete also columns and not
entire rows then it will be welcomed :)