hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Huaxiang Sun <h...@cloudera.com>
Subject Re: Cell Level TTL And hfile.format.version
Date Fri, 06 May 2016 16:39:14 GMT
Hi Saad,

   Please see HBASE-14730 <https://issues.apache.org/jira/browse/HBASE-14730>. With
hfile.format.version 2, it will work partially. As long as the cells are in the memstore,
the TTL tag will be honored.
  Once they are flushed into hfiles, ttl tag is lost which means cells will be there forever.
   Your db will have cells which are supposed to be cleaned up with ttl. Suggest to change
the hfile format to version 3.


> On May 6, 2016, at 6:43 AM, Saad Mufti <saad.mufti@gmail.com> wrote:
> HI,
> We're running a  CDH 5.5.2 HBase cluster (HBase Version 1.0.0-cdh5.5.2,
> revision=Unknown). We are using the per-cell TTL feature (Mutation.setTTL)
> As I learn more about and read up on HBase, I realized that in our HBase
> config hfile.format.version was set to 2 (the default, we haven't touched
> this config yet), and from what I read that version of the HFile format
> does NOT support cell tags which are needed for cell TTL which use tags.
> Of course I am in the process of writing a test to check whether our
> production db is indeed getting filled with cells that should in actuality
> be expired given their TTL value.
> We haven't seen any errors at runtime, does this mean our efforts to set a
> TTL are being silently ignored? Isn't this bad behavior? Even if the
> hfile.format.version is set to the wrong version, wouldn't it be better to
> throw an error instead of just silently dropping any tags that are set?
> Thanks.
> -----
> Saad

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message