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 <[email protected]> To: user <[email protected]>; lars hofhansl <[email protected]> Sent: 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 <[email protected]>: > 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 <[email protected]> > To: "[email protected]" <[email protected]> > 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? >
