Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@locus.apache.org Received: (qmail 8384 invoked from network); 19 Sep 2008 19:43:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Sep 2008 19:43:42 -0000 Received: (qmail 48474 invoked by uid 500); 19 Sep 2008 19:43:38 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 48460 invoked by uid 500); 19 Sep 2008 19:43:38 -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 48449 invoked by uid 99); 19 Sep 2008 19:43:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2008 12:43:38 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.203.238.117] (HELO dns.duboce.net) (63.203.238.117) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2008 19:42:39 +0000 Received: by dns.duboce.net (Postfix, from userid 1008) id 9C96BC51D; Fri, 19 Sep 2008 11:09:37 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on dns.duboce.net X-Spam-Level: Received: from durruti.desk.hq.powerset.com (durruti.desk.hq.powerset.com [208.84.6.246]) by dns.duboce.net (Postfix) with ESMTP id 6A5ADC1CE for ; Fri, 19 Sep 2008 11:09:33 -0700 (PDT) Message-ID: <48D400C5.5030803@duboce.net> Date: Fri, 19 Sep 2008 12:43:01 -0700 From: stack User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: hbase-user@hadoop.apache.org Subject: Re: Why timestamp only return results whose timestamp <= this value References: <904471f90809190845h79be8e30s692000109e3a897e@mail.gmail.com> <48D3CCA7.9090009@duboce.net> <904471f90809191236k2e5c1aefs68d1bd9151e7fd40@mail.gmail.com> In-Reply-To: <904471f90809191236k2e5c1aefs68d1bd9151e7fd40@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.4 Is HBASE-33 what you need? St.Ack Dingding Ye wrote: > For example, i store some urls in the table. I want to find the urls > which are added today. > > i would like to specify the time to the beginning of today and get the > urls newer than the timestamp. > But the problem now is that the api will return the urls older than > the timestamp, but newer than the timestamp. > > What's the main thoughts to design such apis that return the older > data? Maybe the answer will help me understand > the project more, :) > > Thanks. > > sishen > > > On Sat, Sep 20, 2008 at 12:00 AM, stack wrote: > >> Dingding Ye wrote: >> >>> The query apis with timestamp such as getRow, getScanner will return >>> results whose timestamp <= this value. >>> But, Is the newer data more important than the older ones? >>> >>> >> Depends on your application but usually yes. >> >> >>> Is there a way to get results whose timestamp >= this value? >>> >>> >>> >> Not at the moment. >> >> Tell us more about your need Sishen. Maybe there is a workaround we can >> figure. >> >> St.Ack >> >>