You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2013/11/13 07:14:19 UTC

[jira] [Commented] (FALCON-190) /api/entities/list should allow the client to query different fields

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

Venkatesh Seetharam commented on FALCON-190:
--------------------------------------------

Can you please add an integration-test at org.apache.falcon.resource.EntityManagerJerseyIT by mimicking #testGetDependencies so you can verify this works. Thanks!


> /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-boolean.patch, 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)