Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 866FA200D24 for ; Tue, 10 Oct 2017 05:46:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8504F160BE0; Tue, 10 Oct 2017 03:46:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CA8BA1609CE for ; Tue, 10 Oct 2017 05:46:08 +0200 (CEST) Received: (qmail 70546 invoked by uid 500); 10 Oct 2017 03:46:07 -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 70534 invoked by uid 99); 10 Oct 2017 03:46:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2017 03:46:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id C1A4B1844EF for ; Tue, 10 Oct 2017 03:46:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id MxKkikGygddZ for ; Tue, 10 Oct 2017 03:46:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id DE5C060D31 for ; Tue, 10 Oct 2017 03:46:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 29CC8E06BB for ; Tue, 10 Oct 2017 03:46:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 097CF24362 for ; Tue, 10 Oct 2017 03:46:03 +0000 (UTC) Date: Tue, 10 Oct 2017 03:46:03 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18957) add test that confirms 2 FamilyFilters in a FilterList using MUST_PASS_ONE operator will return results that match either of the FamilyFilters and revert as needed to make it pass. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 10 Oct 2017 03:46:09 -0000 [ https://issues.apache.org/jira/browse/HBASE-18957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198118#comment-16198118 ] Duo Zhang commented on HBASE-18957: ----------------------------------- The commits you reverted aim to fix other strange behaviors. IIRC, in a FilterList with OR, if one filter returns NEXT_COLUMN and another returns INCLUDE, is it valid to still passes the cells from same column to the filter which returns NEXT_COLUMN? And for now, NEXT_ROW is ambiguous as a filter will be shared across multiple StoreScanners, and we will only bypass the current family when NEXT_ROW , so a filter can still receive the cells from the same row but another family. How do we want to solve this problem? Thanks. > add test that confirms 2 FamilyFilters in a FilterList using MUST_PASS_ONE operator will return results that match either of the FamilyFilters and revert as needed to make it pass. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: HBASE-18957 > URL: https://issues.apache.org/jira/browse/HBASE-18957 > Project: HBase > Issue Type: Sub-task > Components: Filters > Reporter: Sean Busbey > Assignee: Peter Somogyi > Priority: Critical > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-18957-branch-1.2.v0.patch, HBASE-18957-branch-1.2.v1.patch, HBASE-18957-branch-1.4.v1.patch, HBASE-18957-branch-1.v1.patch, HBASE-18957-master.v1.patch > > > we need a test that shows the expected behavior for filter lists that rely on OR prior to our filterlist improvements so we have a baseline to show compatibility (and/or document incompatibilities that end up being introduced). > Specifically (paraphrased from HBASE-18368 description): Using 2 FamilyFilters in a FilterList using MUST_PASS_ONE operator should return results that match either of the FamilyFilters. -- This message was sent by Atlassian JIRA (v6.4.14#64029)