[
https://issues.apache.org/jira/browse/HBASE-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554792#comment-14554792
]
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/12734605/5980v5.txt
against master branch at commit e1e8434340f02907976f20566c3e55d8d627d4c4.
ATTACHMENT ID: 12734605
{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/14150//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: New Feature
> Components: Client, metrics, Operability, regionserver
> Affects Versions: 0.95.2
> Reporter: Todd Lipcon
> Assignee: Jonathan Lawlor
> Priority: Minor
> Fix For: 2.0.0, 1.2.0
>
> Attachments: 5980v5.master.txt, 5980v5.txt, 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)
