Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@locus.apache.org Received: (qmail 9972 invoked from network); 28 Apr 2008 21:39:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Apr 2008 21:39:39 -0000 Received: (qmail 91206 invoked by uid 500); 28 Apr 2008 21:39:40 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 91189 invoked by uid 500); 28 Apr 2008 21:39:40 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 91178 invoked by uid 99); 28 Apr 2008 21:39:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Apr 2008 14:39:40 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Apr 2008 21:38:55 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 1EC4F234C127 for ; Mon, 28 Apr 2008 14:35:58 -0700 (PDT) Message-ID: <250159868.1209418558124.JavaMail.jira@brutus> Date: Mon, 28 Apr 2008 14:35:58 -0700 (PDT) From: "Bryan Duxbury (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Commented: (HBASE-47) option to set TTL for columns in hbase MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592903#action_12592903 ] Bryan Duxbury commented on HBASE-47: ------------------------------------ For starters let me note that it appears this patch was cut against 0.2, not 0.1. Patch should be relabeled appropriately. HColumnDescriptor * Let's add a constant to HConstants called "FOREVER" and use that in the code wherever the TTL should be unlimited. Also, can we make it's value -1 instead of 0? Memcache * Why the use of Date class instead of System.currentTimeMillis()? Is there something I'm missing? HStore * In getFull, you do the filtering for expired cells at the store level instead of when you're actually iterating. Why not just not add the cells to the results array at all? You'll use less memory. * Same as above in get. > option to set TTL for columns in hbase > -------------------------------------- > > Key: HBASE-47 > URL: https://issues.apache.org/jira/browse/HBASE-47 > Project: Hadoop HBase > Issue Type: New Feature > Components: hql, regionserver > Reporter: Billy Pearson > Priority: Minor > Attachments: hbase-ttl-0.1.patch > > > I would like to see the option to have a TTL on the columns in hbase this feature could be helpfully in removing stale data from large datasets with out havening to do a full scan of the dataset and then issuing deletes. > Example > Say I am crawling pages and only refreshing pages based on a set score and some pages doe not get updated over X days the old version of the page gets removed from the data set. > Say I am striping out links form html and storing them say a link is removed from a page then I would need to issue a delete statement to remove that links form the data set with a ttl the link data would remove its self if not updated in x secs. These are just examples based on crawling like nutch but I can foresee many apps using this option. > This is a feature in bigtables thats is handled when bigtable does garbage-collection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.