Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 1 Mar 2011 19:58:37 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <208977718.5949.1299009517477.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (HBASE-2166) Inconsistent/wrong treatment of
 timestamp parameters in the old Thrift API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-2166:
------------------------------

This just came up again on the list, Usman Waheed.

> 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
>    Affects Versions: 0.20.2
>            Reporter: Lars Francke
>            Assignee: 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira