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 962A2DF38 for ; Thu, 16 Aug 2012 15:13:39 +0000 (UTC) Received: (qmail 53773 invoked by uid 500); 16 Aug 2012 15:13:39 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 53708 invoked by uid 500); 16 Aug 2012 15:13:39 -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 53477 invoked by uid 99); 16 Aug 2012 15:13:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Aug 2012 15:13:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 572182C5BF1 for ; Thu, 16 Aug 2012 15:13:38 +0000 (UTC) Date: Fri, 17 Aug 2012 02:13:38 +1100 (NCT) From: "Alex Baranau (JIRA)" To: issues@hbase.apache.org Message-ID: <1078357512.19175.1345130018357.JavaMail.jiratomcat@arcas> In-Reply-To: <140307823.10335.1315609448897.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-4364) Filters applied to columns not in the selected column list are ignored 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-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436027#comment-13436027 ] Alex Baranau commented on HBASE-4364: ------------------------------------- @Jie Yeah, seems you are right. The problem I'm referring to is a bit different. Now that I re-read the issue description I think that two problems could be contradictory: 1. In this issue it is stated that *filters should be applied to the columns not in the selected list* 2. In the problem I'm referring to states that *filters should not be applied to the columns in the selected list* May be what I'm pointing out with the unit-test is really not a bug, but "designed to be" so? Though it might be not, because it would make scanner to always fetch (physically from the storage) even those columns we are not interested in if filters are added to the scan. Which might add a lot of unnecessary work (currently - when data is in different columnfamilies, or in future for same CF if the storage format will be improved somehow that will allow avoid reading columns that are not requested from single CF). I'd say it may be better to require users to specify explicitly columns to which the filters should be applied iff they are not in the selected list. In case of SingleColumnValueFilter, we may say that user specifies the column explicitly. I.e. we should also have ability, (or do we already?) for filter to add a column to that "apply filter to but not transfer to the user" column list. > Filters applied to columns not in the selected column list are ignored > ---------------------------------------------------------------------- > > Key: HBASE-4364 > URL: https://issues.apache.org/jira/browse/HBASE-4364 > Project: HBase > Issue Type: Bug > Components: filters > Affects Versions: 0.90.4, 0.92.0, 0.94.0 > Reporter: Todd Lipcon > Priority: Critical > Attachments: HBASE-4364-failing-test-with-simplest-custom-filter.patch, hbase-4364_trunk.patch, hbase-4364_trunk-v2.patch > > > For a scan, if you select some set of columns using addColumns(), and then apply a SingleColumnValueFilter that restricts the results based on some other columns which aren't selected, then those filter conditions are ignored. -- 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