You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Blaye Nicolas (JIRA)" <ji...@apache.org> on 2016/06/24 12:33:16 UTC
[jira] [Updated] (HBASE-16106) HBase Rest API: unexpected behavior
of get with timestamp
[ https://issues.apache.org/jira/browse/HBASE-16106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Blaye Nicolas updated HBASE-16106:
----------------------------------
Description:
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.
was:
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.
> 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)