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] [Updated] (FALCON-190) /api/entities/list should allow the client to query different fields
Date Wed, 13 Nov 2013 05:58:18 GMT

     [ https://issues.apache.org/jira/browse/FALCON-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Haohui Mai updated FALCON-190:
------------------------------

    Description: 
FALCON-171 returns the status of each entity in /api/entities/list. Getting the status of
an entity requires RPC calls, where in some use cases the client might want to avoid the overhead.

This jira proposes an extensible API to specify the fields that the client is interested in,
so that the client can pay the overhead of querying additional fields only when it needs to.

  was: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.


> /api/entities/list should allow the client to query different fields
> --------------------------------------------------------------------
>
>                 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
>            Assignee: Haohui Mai
>         Attachments: FALCON-190.000.patch
>
>
> FALCON-171 returns the status of each entity in /api/entities/list. Getting the status
of an entity requires RPC calls, where in some use cases the client might want to avoid the
overhead.
> This jira proposes an extensible API to specify the fields that the client is interested
in, so that the client can pay the overhead of querying additional fields only when it needs
to.



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

Mime
View raw message