<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Does TTL in Hbase require Major Compaction? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Does-TTL-in-Hbase-require-Major-Compaction/m-p/214167#M176082</link>
    <description>&lt;P&gt;  The docs say:&lt;/P&gt;&lt;P style="margin-left: 20px;"&gt;When an explicit deletion occurs in HBase, the data is not actually deleted. Instead, a &lt;EM&gt;tombstone&lt;/EM&gt; marker is written. The tombstone marker prevents the data from being returned with queries. During a major compaction, the data is actually deleted, and the tombstone marker is removed from the StoreFile. &lt;STRONG&gt;If the deletion happens because of an expired TTL, no tombstone is created. Instead, the expired data is filtered out and is not written back to the compacted StoreFile.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;What does "expired data is filtered out and is not written back to the compacted StoreFile." mean?&lt;/P&gt;&lt;P&gt;I have done some testing with TTL.  I put 1 million records in a database.  I checked the file size.  Then I set the ttl to 1 minute and all the data dissapeared (the actual file got much smaller).  Our database has major compaction shut off.&lt;/P&gt;&lt;P&gt;Does a major compaction have to happen with TTL?&lt;/P&gt;</description>
    <pubDate>Thu, 22 Jun 2017 00:53:45 GMT</pubDate>
    <dc:creator>juchems_mark_e</dc:creator>
    <dc:date>2017-06-22T00:53:45Z</dc:date>
  </channel>
</rss>

