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

Hadoop QA commented on HBASE-5980:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12734208/5980v5.txt
  against master branch at commit 7f2b33dbbf90474a8f73e4d38ea8f6817ee3dcdb.
  ATTACHMENT ID: 12734208

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

    {color:green}+1 tests included{color}.  The patch appears to include 2 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/14125//console

This message is automatically generated.

> Scanner responses from RS should include metrics on rows/KVs filtered
> ---------------------------------------------------------------------
>
>                 Key: HBASE-5980
>                 URL: https://issues.apache.org/jira/browse/HBASE-5980
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client, metrics, regionserver
>    Affects Versions: 0.95.2
>            Reporter: Todd Lipcon
>            Assignee: Jonathan Lawlor
>            Priority: Minor
>         Attachments: 5980v5.txt, 5980v5.txt, 5980v5.txt, 
> HBASE-5980-branch-1.patch, HBASE-5980-v1.patch, HBASE-5980-v2.patch, 
> HBASE-5980-v2.patch, HBASE-5980-v3.patch, HBASE-5980-v4.patch
>
>
> Currently it's difficult to know, when issuing a filter, what percentage of 
> rows were skipped by that filter. We should expose some basic counters back 
> to the client scanner object. For example:
> - number of rows filtered by row key alone (filterRowKey())
> - number of times each filter response was returned by filterKeyValue() - 
> corresponding to Filter.ReturnCode
> What would be slickest is if this could actually return a tree of counters 
> for cases where FilterList or other combining filters are used. But a 
> top-level is a good start.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to