hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-2166) Inconsistent/wrong treatment of timestamp parameters in the old Thrift API
Date Mon, 14 Apr 2014 15:46:16 GMT

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

A B commented on HBASE-2166:
----------------------------

I use thrift 0.9.1.
When i put data into database (mutateRowTs), i use a number for the timestamp.
Reading data from database with a number as timestamp woudn't find any data.
I found a awful workaroud .... I use a string as timestring and it works.

mutateRowTs ('tab', 'key', 1234567890 ...)
getRowTs  ('tab', 'key', '1234567890' ...)



> Inconsistent/wrong treatment of timestamp parameters in the old Thrift API
> --------------------------------------------------------------------------
>
>                 Key: HBASE-2166
>                 URL: https://issues.apache.org/jira/browse/HBASE-2166
>             Project: HBase
>          Issue Type: Bug
>          Components: Thrift
>            Reporter: Lars Francke
>
> The old Thrift API treats timestamps wrong/inconsistent.
> getRowTs should return a specific version or null if that doesn't exist. Currently it
does seem to treat the timestamp as exclusive so the row is not found. Same goes for getVerTs
but there it might only be a documentation problem.
> I'll go through the old API and will try to find any such problems and correct them in
a way that is consistent with the Java API where possible.
> Peter Falk reported this on the mailing list. Thanks!



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message