[
https://issues.apache.org/jira/browse/HBASE-11026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974801#comment-13974801
]
Hadoop QA commented on HBASE-11026:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12640942/HBASE-11026_1.patch
against trunk revision .
ATTACHMENT ID: 12640942
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified tests.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 javac{color}. The patch appears to cause mvn compile goal to
fail.
{color:red}-1 findbugs{color}. The patch appears to cause Findbugs
(version 1.3.9) to fail.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9343//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9343//console
This message is automatically generated.
> Provide option to filter out all rows in PerformanceEvaluation tool
> -------------------------------------------------------------------
>
> Key: HBASE-11026
> URL: https://issues.apache.org/jira/browse/HBASE-11026
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.99.0
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.99.0
>
> Attachments: HBASE-11026_1.patch
>
>
> Performance Evaluation could also be used to check the actual performance of
> the scans on the Server side by passing Filters that filters out all the
> rows. We can create a test filter and add it to the Filter.proto and set
> this filter based on input params. Could be helpful in testing.
> If you feel this is not needed pls feel free to close this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
