Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 431C417F6D for ; Mon, 27 Apr 2015 21:44:44 +0000 (UTC) Received: (qmail 40428 invoked by uid 500); 27 Apr 2015 21:44:44 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 40380 invoked by uid 500); 27 Apr 2015 21:44:44 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 40367 invoked by uid 99); 27 Apr 2015 21:44:44 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Apr 2015 21:44:44 +0000 Date: Mon, 27 Apr 2015 21:44:43 +0000 (UTC) From: "Jonathan Lawlor (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-5980) Scanner responses from RS should include metrics on rows/KVs filtered MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Lawlor updated HBASE-5980: ----------------------------------- Status: Patch Available (was: Reopened) > 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: HBASE-5980-v1.patch, HBASE-5980-v2.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)