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 6A989DCDB for ; Tue, 31 Jul 2012 06:00:41 +0000 (UTC) Received: (qmail 77055 invoked by uid 500); 31 Jul 2012 06:00:40 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 76829 invoked by uid 500); 31 Jul 2012 06:00:40 -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 76760 invoked by uid 99); 31 Jul 2012 06:00:38 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jul 2012 06:00:38 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id C44BA14285B for ; Tue, 31 Jul 2012 06:00:37 +0000 (UTC) Date: Tue, 31 Jul 2012 06:00:37 +0000 (UTC) From: "Shrijeet Paliwal (JIRA)" To: issues@hbase.apache.org Message-ID: <508162974.120134.1343714437805.JavaMail.jiratomcat@issues-vm> In-Reply-To: <322155279.111994.1343425474806.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HBASE-6468) RowCounter may return incorrect result if column name is specified in command line 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-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425548#comment-13425548 ] Shrijeet Paliwal commented on HBASE-6468: ----------------------------------------- {quote} FirstKeyValueMatchingQualifiersFilter -> When a CF contains qualifier a,b,c and the qualifiers provided are b and c, what will happen to the KVs for qualifier 'a' ? Will this be included in the Result? Is this expected? {quote} Depends on whether or not first KV matching any of the columns associated with filter have been seen yet or not. {quote} Can the qualifiers be accommodated in FirstKeyOnlyFilter only? Do we need a new Filter? Just a though from my side. By default FirstKeyOnlyFilter allow only the 1st KV (from all the qualifiers) from a CF to come in the Result and will filter out other KVs. Specifying a set of qualifiers to FirstKeyOnlyFilter will restrict the selection of the 1st KV from a any of these qualifiers only. It will filter out all KVs from other qualifiers. {quote} FKVMatchingQualifiersFilter has a peculiar behavior hence (extending it from FirstKeyOnlyFilter and) creating a new filter made sense. > RowCounter may return incorrect result if column name is specified in command line > ---------------------------------------------------------------------------------- > > Key: HBASE-6468 > URL: https://issues.apache.org/jira/browse/HBASE-6468 > Project: HBase > Issue Type: Bug > Affects Versions: 0.90.5 > Reporter: Shrijeet Paliwal > Attachments: 0001-HBASE-6468-RowCounter-may-return-incorrect-result.patch, 0002-HBASE-6468-RowCounter-may-return-incorrect-result.patch > > > The RowCounter use FirstKeyOnlyFilter regardless of whether or not the > command line argument specified a column family (or family:qualifier). > In case when no qualifier was specified as argument, the scan will > give correct result. However in the other case the scan instance may > have been set with columns other than the very first column in the > row, causing scan to get nothing as the FirstKeyOnlyFilter removes > everything else. > https://issues.apache.org/jira/browse/HBASE-6042 is related. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira