hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junegunn Choi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16106) HBase Rest API: unexpected behavior of get with timestamp
Date Wed, 29 Jun 2016 02:30:45 GMT

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

Junegunn Choi commented on HBASE-16106:
---------------------------------------

[~Whitefret] To retrieve multiple versions, you have to set {{v}} field of the query string
to a number larger than 1. e.g. {{?v=3}}, and of course the column family should be configured
to hold more than one versions. The behavior is consistent with Java client API where you
only get one version unless otherwise specified.

> HBase Rest API: unexpected behavior of get with timestamp
> ---------------------------------------------------------
>
>                 Key: HBASE-16106
>                 URL: https://issues.apache.org/jira/browse/HBASE-16106
>             Project: HBase
>          Issue Type: Bug
>          Components: API, REST
>    Affects Versions: 1.2.1
>            Reporter: Blaye Nicolas
>            Priority: Minor
>              Labels: easyfix, newbie
>
> Issue seen there: http://stackoverflow.com/questions/37985426/hbase-get-request-for-row-data-with-timestamp?noredirect=1#comment63464266_37985426
 
> The  *adress:port/table/row/column/timestamp* returns the first value *strictly inferior*
to the timestamp provided.  
> This behavior is not the one seen in bash and java as explained in the question.  
> I haven't found the bug here but I may be wrong, and it may be fixed already. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message