Vladimir Rodionov 2012-06-05, 18:19
Andrew Purtell 2012-06-06, 07:59
Vladimir Rodionov 2012-06-06, 17:59
Daniel Iancu 2012-06-08, 16:47
Anoop Sam John 2012-07-04, 07:04
Andrew Purtell 2012-06-06, 07:53
Anoop Sam John 2012-06-06, 08:08
Andrew Purtell 2012-06-06, 08:42
Vladimir Rodionov 2012-06-05, 18:44
Stack 2012-06-05, 18:43
Vladimir Rodionov 2012-06-05, 19:00
-RE: Some suggestions for future features
Anoop Sam John 2012-06-05, 19:15
>3. Row prefix delete operation - Delete all rows which starts with a 'prefix'
Sometime back I was thinking about this. One usage came for us.[Which was low prioritized later ] I will try to work on this soon.
From: Vladimir Rodionov [[EMAIL PROTECTED]]
Sent: Wednesday, June 06, 2012 12:30 AM
To: [EMAIL PROTECTED]
Subject: RE: Some suggestions for future features
My bad, getting through all HBase API is not easy task. I will look at Coprocessor. more closely
Custom Key comparator allows to perform some useful tricks such as:
keeping rows in a chronological order (temporal locality) and allowing to access them by some rowid at the same time.
We preserve temporal locality for rows and access to the rows by ID at the same time
Although, HBase does not support Get by row prefix API call we can use Scanner for that purpose.
Principal Platform Engineer
Carrier IQ, www.carrieriq.com
e-mail: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] [[EMAIL PROTECTED]] On Behalf Of Stack [[EMAIL PROTECTED]]
Sent: Tuesday, June 05, 2012 11:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Some suggestions for future features
On Tue, Jun 5, 2012 at 11:19 AM, Vladimir Rodionov
<[EMAIL PROTECTED]> wrote:
> 1. Custom Key, KeyValue, Row Comparators (per HTable). I went through the 0.92 API and it seems that adding this feature is going to be hard task. There are a lot of places all over HBase source code
> where KeyValue static class members are accessed directly.
Yes. Its our most fundamental class. Its tough to change since it
there are a bunch of perf. fixes and a bunch of the upper tiers key
off its format (and as you note, make direct calls against this
That said, there is pressure building that KV should be an Interface
only because others want to mess w/ its implementation (improve our
What would you like to do Vladimir? You want to change comparators?
> 2.Compaction callback. Can be HTable as well. Something like this one:
> public interface CompactionCallback<KeyValue>
> public void preCompact(KeyValue kv, CompactionContext ctx)
Is this not in Coproccessors now? See trunk. See Compactor.java down
around #136 where the scanner used compacting is overrideable.
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.
Ian Varley 2012-06-05, 19:34
Vladimir Rodionov 2012-06-05, 20:32
Anoop Sam John 2012-06-06, 03:42
lars hofhansl 2012-06-06, 09:11
Anoop Sam John 2012-06-06, 10:02