hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Demai Ni <nid...@gmail.com>
Subject Re: a way to record # of rows 'deleted' due to TTL
Date Sat, 19 Apr 2014 00:01:10 GMT
Lars,

thanks a lot for the tip. seems not a straightforward one. I will look into
ExplicitColumnTracker and ScanQueryMatcher. I agree compaction time may be
a good idea.

Demai


On Fri, Apr 18, 2014 at 2:52 PM, lars hofhansl <larsh@apache.org> wrote:

> There is no good way at the moment unless you handle it completely
> yourself via a coprocessor.
> I suppose we could add a metric...? Would that be good enough? Even that
> would not be entirely trivial to add into the bowls of the ColumnTrackers
> (wouldn't want to count it during normal scans but only in compactions).
>
>
> -- Lars
>
>
>
> ________________________________
>  From: Demai Ni <nidmgg@gmail.com>
> To: "dev@hbase.apache.org" <dev@hbase.apache.org>
> Sent: Friday, April 18, 2014 2:27 PM
> Subject: a way to record # of rows 'deleted' due to TTL
>
>
> hi, folks,
>
> Understand that TTL plays its role in the background, I am wondering
> whether there is a way to have some information of the retired rows?
>
> for example,
> 1) 100 rows were put initially
> 2) during one day period, 2 rows was deleted by user, and 10 rows 'retired'
> due to TTL
>
> is there a way to figure out the '10'? Is there a way to plug in a
> co-processor for that purpose?
>
> Many thanks
>
> Demai
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message