falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-171) Provide status in /api/entities/list
Date Wed, 13 Nov 2013 01:54:17 GMT

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

Srikanth Sundarrajan commented on FALCON-171:
---------------------------------------------

The older list call 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. Created FALCON-190 to track
this. If 0.4 release does go out with the current behavior, users in larger deployments might
be hurt adversely.

> Provide status in /api/entities/list
> ------------------------------------
>
>                 Key: FALCON-171
>                 URL: https://issues.apache.org/jira/browse/FALCON-171
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: general
>    Affects Versions: 0.3
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>             Fix For: 0.4
>
>         Attachments: FALCON-171.000.patch
>
>
> The Web UI calls the REST api /api/entities/list to get the lists of available feeds
/ processes / clusters.
> The current implementation does not provide the status field, which forces the UI to
make separate REST calls to get the information. The list API should provide the status field
directly in the results.



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

Mime
View raw message