hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lars hofhansl <la...@apache.org>
Subject Re: Coprocessor beacuse of TTL expired?
Date Mon, 21 Jul 2014 14:27:08 GMT
HBASE-11054 is about delete trackers (i.e. when/how delete markers are enforced), TTL is handled
differently. One could ask why these are handled differently of course.

 From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
To: user <user@hbase.apache.org>; lars hofhansl <larsh@apache.org> 
Subject: Re: Coprocessor beacuse of TTL expired?

I had open 10115 a while back but I think  11054 mostly covers it. But this
was exactly the idea behind 10115.

2014-07-21 10:19 GMT-04:00 lars hofhansl <larsh@apache.org>:

> It's possible but ... uhm... Tedious. You would have to use the pre flush
> and compaction scanner open hooks, do the TTL calculation yourself for each
> KeyValue that passes through the scanner and then act accordingly.
> Checkout RegionObserver.preCompactScannerOpen(...) and
> preFlushScannerOpen(...)
> It's possible we could add something like this.
> -- Lars
> ________________________________
>  From: Guillermo Ortiz <konstt2000@gmail.com>
> To: "user@hbase.apache.org" <user@hbase.apache.org>
> Sent: Monday, July 21, 2014 5:24 AM
> Subject: Coprocessor beacuse of TTL expired?
> I want to use coprocessors (observers), Could I execute an coprocessors
> which executes my code when a row expired because the TTL has expired?
> will it be executed automatically? I mean,, without any scan or get over
> that row?? it's a pre and post delete or which observer?
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message