Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 2 Apr 2012 18:03:23 +0000 (UTC)
From: "stack (Resolved) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <706898222.1615.1333389803902.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <599912265.3838.1333316788127.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HBASE-5694) getRowsWithColumnsTs() in Thrift
 service handles timestamps incorrectly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-5694.
--------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.92.2)
                   0.94.0
     Hadoop Flags: Reviewed

Applied to 0.94 and to trunk.  Thanks for the patch Wouter (I ran testthriftserver local and it passed).  Doesn't look like thrift2 has similar code so passed on trying to apply the patch there.
                
> getRowsWithColumnsTs() in Thrift service handles timestamps incorrectly
> -----------------------------------------------------------------------
>
>                 Key: HBASE-5694
>                 URL: https://issues.apache.org/jira/browse/HBASE-5694
>             Project: HBase
>          Issue Type: Bug
>          Components: thrift
>    Affects Versions: 0.92.1
>            Reporter: Wouter Bolsterlee
>             Fix For: 0.94.0
>
>         Attachments: HBASE-5694-trunk-20120402.patch, HBASE-5694.patch
>
>
> The getRowsWithColumnsTs() method in the Thrift interface only applies the timestamp if columns are explicitly specified. However, this method also allows for columns to be unspecified (this is even used internally to implement e.g. getRows()). The cause of the bug is a minor scoping issue: the time range is set inside a wrong if statement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira