Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 7 Apr 2011 10:48:05 +0000 (UTC)
From: "Eric Charles (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2111188423.40418.1302173285736.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <298860.32509.1301926685973.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-3729) Get cells via shell with a time
 range predicate
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016800#comment-13016800 ] 

Eric Charles commented on HBASE-3729:
-------------------------------------

Hi, i tried to remove/add in .rb, but was a bit lost with the patch history.
Anyway, I understand last Ted's code lines, and it should shell should map the API.

Tks again for this. Looking for it in trunk.

PS: I will crawl the archives to have a better understanding on the reason to return only the last version by default when timerange set.


> Get cells via shell with a time range predicate
> -----------------------------------------------
>
>                 Key: HBASE-3729
>                 URL: https://issues.apache.org/jira/browse/HBASE-3729
>             Project: HBase
>          Issue Type: New Feature
>          Components: shell
>            Reporter: Eric Charles
>            Assignee: Ted Yu
>         Attachments: 3729-v2.txt, 3729-v3.txt, 3729-v4.txt, 3729.txt
>
>
> HBase shell allows to specify a timestamp to get a value
> - get 't1', 'r1', {COLUMN => 'c1', TIMESTAMP => ts1}
> If you don't give the exact timestamp, you get nothing... so it's difficult to get the cell previous versions.
> It would be fine to have a "time range" predicate based get.
> The shell syntax could be (depending on technical feasibility)
> - get 't1', 'r1', {COLUMN => 'c1', TIMERANGE => (start_timestamp, end_timestamp)}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira