hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7953) Some HFilePerformanceEvaluation tests might fail because of scanner.getValue when there is no more row
Date Sat, 23 Mar 2013 12:47:16 GMT

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

Hadoop QA commented on HBASE-7953:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12575183/HBASE-7953-v3-0.94.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/4984//console

This message is automatically generated.
                
> Some HFilePerformanceEvaluation tests might fail because of scanner.getValue when there
is no more row
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-7953
>                 URL: https://issues.apache.org/jira/browse/HBASE-7953
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jean-Marc Spaggiari
>            Assignee: Jean-Marc Spaggiari
>             Fix For: 0.98.0
>
>         Attachments: HBASE-7953-v0-trunk.patch, HBASE-7953-v1-trunk.patch, HBASE-7953-v2-trunk.patch,
HBASE-7953-v3-0.94.patch, HBASE-7953-v3-trunk.patch
>
>
> There is 2 places in the code (Both trunk and 0.94) where we are trying to get the row
value even when scanner.next() returned null. Need to fix that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message