Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 17805 invoked from network); 3 Feb 2009 20:11:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Feb 2009 20:11:28 -0000 Received: (qmail 12641 invoked by uid 500); 3 Feb 2009 20:11:27 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 12618 invoked by uid 500); 3 Feb 2009 20:11:27 -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 12607 invoked by uid 99); 3 Feb 2009 20:11:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Feb 2009 12:11:27 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tmnichols@gmail.com designates 209.85.221.20 as permitted sender) Received: from [209.85.221.20] (HELO mail-qy0-f20.google.com) (209.85.221.20) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Feb 2009 20:11:19 +0000 Received: by qyk13 with SMTP id 13so3217231qyk.5 for ; Tue, 03 Feb 2009 12:10:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=nLRqZ6XZTo26a0r4lNiL9vlTQHn10ob0mXjp2NErR+I=; b=DvCaSzOojR4UGjaP0zIPgNazjg2XBojhx+Cz7oF4xTk+94/6KFgZRp6UrIXvQHZ26F jJA0vSchnOwGrPPY6CjJG5nPwsFRyxcapp8R32AOGFyQYkNS7I5/XmdnLWe+IXXSJwxK tXDejZPoFJLhP8FUTroYyriyvXy0R3a35Q58o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=B+BY5UaCwf4yT41MDoBeVqFwveHFa0f2HUyaMwZxjZ0H0E0TG/x5qcVoG0Ur99DICH 7syvu18RTuyx+bqf8BARQ9D4pyFjoNc35xOBeGYWz+YTgZz5eNeGQPZMsloqtaBb5Pm/ JSgX8GUgeeR5Cos0CWk2qC7YmK8Sqf6Eglsy0= MIME-Version: 1.0 Received: by 10.215.66.14 with SMTP id t14mr8974414qak.321.1233691858776; Tue, 03 Feb 2009 12:10:58 -0800 (PST) In-Reply-To: <1f2501c98633$98ee06c0$caca1440$@com> References: <1f2501c98633$98ee06c0$caca1440$@com> Date: Tue, 3 Feb 2009 15:10:58 -0500 Message-ID: Subject: Re: Scan for timestamp > some time From: Tom Nichols To: hbase-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Jonathan, Thanks for the update. Here's the feature request. https://issues.apache.org/jira/browse/HBASE-1182 What's the timeline for the API redesign (HBASE-880)? If possible, it would be nice for this to be addressed sooner if that feature is still a long ways away from a release. Thanks. -Tom On Tue, Feb 3, 2009 at 2:14 PM, Jonathan Gray wrote: > Tom, > > This is not currently possible. > > The functionality you describe might be included as part of HBASE-880, > however it could be implemented with a Filter. > > Unfortunately it wouldn't be as easy as writing a new Class implementing > RowFilterInterface because RFI.filterColumn() and RFI.filterRow() do not > take timestamp. So you'd need to update RFI as well as the calls to filters > in the scanner code. > > Either way, it is a valid feature request. > > JG > >> -----Original Message----- >> From: Tom Nichols [mailto:tmnichols@gmail.com] >> Sent: Tuesday, February 03, 2009 10:47 AM >> To: hbase-user@hadoop.apache.org >> Subject: Scan for timestamp > some time >> >> Hi, >> >> I'm interesting in scanning for all columns inserted _after_ a certain >> timestamp. The getScanner methods that take a timestamp return all >> columns _before_ that time. Is there any way for me to accomplish >> what I'm trying to do without sending gobs of results over the wire >> that I have no interest in? Is this possible maybe via a >> RowFilterInterface impl? >> >> If it's not doable currently, is it a valid feature request? >> >> Thanks in advance. >> -Tom > >