Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.incubator.apache.org
Date: Wed, 13 Nov 2013 03:55:17 +0000 (UTC)
From: "Haohui Mai (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12678927.1384307485051.63264.1384314917830@arcas>
In-Reply-To: <JIRA.12678927.1384307485051@arcas>
References: <JIRA.12678927.1384307485051@arcas>
Subject: [jira] [Commented] (FALCON-190) Provide status conditionally in
 /api/entities/list and not always
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FALCON-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820903#comment-13820903 ] 

Haohui Mai commented on FALCON-190:
-----------------------------------

We've considered it and FALCON-171 is intended to be a short-term solution for the web UI. This API should have a parameter to return the value of the fields that the users are interested in.


> Provide status conditionally in /api/entities/list and not always
> -----------------------------------------------------------------
>
>                 Key: FALCON-190
>                 URL: https://issues.apache.org/jira/browse/FALCON-190
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: general
>    Affects Versions: 0.4
>            Reporter: Srikanth Sundarrajan
>
> The list call prior to FALCON-171 comes back in a jiffy as it doesn't talk to the scheduler to get the status. To default the list to include the status can make this call quite slow, particularly when you have few hundred feeds / processed distributed across colos.


--
This message was sent by Atlassian JIRA
(v6.1#6144)