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 5E1D717704 for ; Thu, 18 Jun 2015 07:58:04 +0000 (UTC) Received: (qmail 29701 invoked by uid 500); 18 Jun 2015 07:58:04 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 29658 invoked by uid 500); 18 Jun 2015 07:58:04 -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 29647 invoked by uid 99); 18 Jun 2015 07:58:04 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jun 2015 07:58:04 +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 CE681182234 for ; Thu, 18 Jun 2015 07:58:03 +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-eu-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 Hgi_9Ay2rCkv for ; Thu, 18 Jun 2015 07:58:03 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id 2A45820F3F for ; Thu, 18 Jun 2015 07:58:02 +0000 (UTC) Received: (qmail 29614 invoked by uid 99); 18 Jun 2015 07:58:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jun 2015 07:58:01 +0000 Date: Thu, 18 Jun 2015 07:58:01 +0000 (UTC) From: "Suhas Vasu (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FALCON-1186) Add filtering capability to result of instance summary 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-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suhas Vasu updated FALCON-1186: ------------------------------- Attachment: FALCON-1186.patch Have added capability to filter based on status & colo. Ordering can be done only on cluster name. Ordering on status doesn't seem so helpful. Also have incorporated changes for FALCON-1208, so that we can filter based on more than one value for any field in instance APIs > Add filtering capability to result of instance summary > ------------------------------------------------------- > > Key: FALCON-1186 > URL: https://issues.apache.org/jira/browse/FALCON-1186 > Project: Falcon > Issue Type: Improvement > Reporter: Suhas Vasu > Assignee: Suhas Vasu > Priority: Minor > Attachments: FALCON-1186.patch > > > Falcon instance summary returns a consolidated instance summary of all instances between the specified time range. > It would be helpful to add filtering capability on this result. > For ex:- Give me all killed instances for a particular time range or Give me all succeeded instances for a time range > This would be really helpful when someone wants to use falcon client methods / API's to do some monitoring on the process instances -- This message was sent by Atlassian JIRA (v6.3.4#6332)