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-190) /api/entities/list should allow the client to query different fields
Date Wed, 13 Nov 2013 07:36:21 GMT

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

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

BTW, AbstractEntityManager::getStatus() is a public API which calls getStatus(Entity entity,
EntityType type). I'm hesitate to pull the code to calculate the status in getEntityList()
into getStatus() since it'll break compatibility...

> /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-190.001.patch,
FALCON-190.002.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