You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Emre Colak (JIRA)" <ji...@apache.org> on 2015/10/16 18:07:05 UTC

[jira] [Created] (HBASE-14630) Cells still show up in scan after cell-level TTL has expired

Emre Colak created HBASE-14630:
----------------------------------

             Summary: Cells still show up in scan after cell-level TTL has expired
                 Key: HBASE-14630
                 URL: https://issues.apache.org/jira/browse/HBASE-14630
             Project: HBase
          Issue Type: Bug
    Affects Versions: 1.1.2, 1.0.2
            Reporter: Emre Colak


I have an HBase table with the following description:

{NAME => 'cf', DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0', VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIONS => '0' , TTL => 'FOREVER', KEEP_DELETED_CELLS => 'FALSE', BLOCKSIZE => '65536', IN_MEMORY => 'false', BLOCKCACHE => 'true'}

I put some values in it and then set TTL (30s) on those values with another
put operation. First thing I notice is that the timestamps of the cells get
updated after the 2nd put. And 30 seconds later, when I do a scan on the
table, I still see those cells in the table, however this time with their
timestamps updated to the original timestamps.

I understand that these cells won't necessarily be deleted until a
compaction, but they still come up in my scan even though the TTL
that I set on them has expired.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)