Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 49356 invoked from network); 1 Apr 2009 13:56:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Apr 2009 13:56:48 -0000 Received: (qmail 57346 invoked by uid 500); 1 Apr 2009 13:56:48 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 57319 invoked by uid 500); 1 Apr 2009 13:56:47 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 57300 invoked by uid 99); 1 Apr 2009 13:56:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 13:56:47 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [207.192.72.253] (HELO shablam.senortoad.com) (207.192.72.253) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 13:56:38 +0000 Received: from [192.168.14.40] (454a27d2.cst.lightpath.net [69.74.39.210]) by shablam.senortoad.com (Postfix) with ESMTPA id 53B7A1405B for ; Wed, 1 Apr 2009 09:56:16 -0400 (EDT) Message-ID: <49D3727F.70800@s7labs.com> Date: Wed, 01 Apr 2009 09:56:15 -0400 From: Wes Chow Organization: S7 Labs User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: hbase-user@hadoop.apache.org Subject: timestamp uses Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org So far, few if any of the schema designs I've come across have really talked about using the timestamp field and HBase's automatic deletion of old cells in a smart way. What is the timestamp typically used for? Snapshotting? Implementing more complicated transactions than HBase natively supports? Wes