falcon-dev mailing list archives

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

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

Haohui Mai commented on FALCON-171:

The api can be even more generic. It is possible to specify a sets of fields that the client
is interested in (e.g., status, colo, description) through the call. It can be addressed in
a separate jira.

For now the web UI is the dominant user for this call, so what do you think we just make this
minimal change and move forward in the short term?

> 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
>            Reporter: Haohui Mai
>         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

View raw message