Thanks :) So if I set MIN_VERSIONS>1, then TTL feature would completely remove experied row? My Idea is to automatically remove experied data. It's ok to see sometimes expired data but not more than for +-2 days (TTL-1 second + 1 day waiting for next major compation).
2014-09-02 23:03 GMT+04:00 lars hofhansl <[email protected]>: > Are these the last versions of a cell? You have MIN_VERSIONS set to 1, > meaning HBase will keep at least one version around regardless of whether > it is expired by TTL or not. > > -- Lars > > > > ________________________________ > From: Serega Sheypak <[email protected]> > To: user <[email protected]> > Sent: Tuesday, September 2, 2014 11:40 AM > Subject: ttl problem, cells are not deleted > > > Hi, I'm trying to use HBase TTL feature > here is table DDL: > > hbase(main):004:0> describe 'item_to_item_similar_rec' > DESCRIPTION > ENABLED > > {NAME => 'my_table', FAMILIES => [{NAME => 'd', DATA_BLOCK_ENCODING => > 'NONE', BLOOMFILTER => 'ROWCOL', REPLI true > > CATION_SCOPE => '0', VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIONS > => '1', TTL => '172800', KEEP_DELETED_CELLS => 'fal > > se', BLOCKSIZE => '65536', IN_MEMORY => 'true', ENCODE_ON_DISK => 'true', > BLOCKCACHE => 'true'}]} > > 1 row(s) in 0.1730 seconds > > It has ttl set to 172800 seconds = 2 days. > I see a cells that are much older than two days: > > column=d:099, timestamp=1409049061509, value=\x01\ > current ts = 1409679511000 > > 1409679511000 - 1409049061509 = 630449491 >
