Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # dev - Some suggestions for future features


Copy link to this message
-
RE: Some suggestions for future features
Vladimir Rodionov 2012-06-06, 17:59
Scan implies scanning table and this is what I would like to avoid. I consider "bulk" delete as a hint (internal filter)
for HBase (RegionServer) execution of which can be deferred  until actual region compaction kicks off.

Why does some one need this for? CF TTL is not enough in some cases and there is need to have more flexible API to perform
HBase housekeeping.

Best regards,
Vladimir Rodionov
Principal Platform Engineer
Carrier IQ, www.carrieriq.com
e-mail: [EMAIL PROTECTED]

________________________________________
From: Andrew Purtell [[EMAIL PROTECTED]]
Sent: Wednesday, June 06, 2012 12:59 AM
To: [EMAIL PROTECTED]
Subject: Re: Some suggestions for future features

For this one...

On Tue, Jun 5, 2012 at 8:19 PM, Vladimir Rodionov
<[EMAIL PROTECTED]> wrote:
> 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.

Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet
Hein (via Tom White)

Confidentiality Notice:  The information contained in this message, including any attachments hereto, may be confidential and is intended to be read only by the individual or entity to whom this message is addressed. If the reader of this message is not the intended recipient or an agent or designee of the intended recipient, please note that any review, use, disclosure or distribution of this message or its attachments, in any form, is strictly prohibited.  If you have received this message in error, please immediately notify the sender and/or [EMAIL PROTECTED] and delete or destroy any copy of this message and its attachments.