Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B73941867B for ; Wed, 7 Oct 2015 03:35:28 +0000 (UTC) Received: (qmail 96090 invoked by uid 500); 7 Oct 2015 03:35:28 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 96043 invoked by uid 500); 7 Oct 2015 03:35:28 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 96032 invoked by uid 99); 7 Oct 2015 03:35:28 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2015 03:35:28 +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 F0838180E1A for ; Wed, 7 Oct 2015 03:35:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.97 X-Spam-Level: X-Spam-Status: No, score=0.97 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id IWPyzaBElhKb for ; Wed, 7 Oct 2015 03:35:27 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 2F1E921270 for ; Wed, 7 Oct 2015 03:35:27 +0000 (UTC) Received: (qmail 96017 invoked by uid 99); 7 Oct 2015 03:35:27 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2015 03:35:27 +0000 Date: Wed, 7 Oct 2015 03:35:26 +0000 (UTC) From: "Venkat Ranganathan (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1490) Support OR in filterBy 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/FALCON-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946181#comment-14946181 ] Venkat Ranganathan commented on FALCON-1490: -------------------------------------------- I think this should be good to begin with. I have not started the discussion on Instance search UI wireframes, so not sure if there will be any more filtering capabilities required. We can go with what we have now and if needed change it. I do see more sophisticated searching to be a requirement as we have more capabilities and integrations (like for atlas) > Support OR in filterBy > ----------------------- > > Key: FALCON-1490 > URL: https://issues.apache.org/jira/browse/FALCON-1490 > Project: Falcon > Issue Type: Sub-task > Components: client > Reporter: sandeep samudrala > Assignee: Narayan Periwal > Priority: Minor > Fix For: 0.8 > > > As of now only AND is supported in filterBy, it would be useful to have OR support too so that users can use filterBy accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)