[
https://issues.apache.org/jira/browse/HBASE-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244086#comment-13244086
]
Hadoop QA commented on HBASE-5694:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520856/HBASE-5694.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1366//console
This message is automatically generated.
> getRowsWithColumnsTs function Thrift service incorrectly handles time range
> ---------------------------------------------------------------------------
>
> 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.92.2
>
> Attachments: 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
