[
https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552548#comment-15552548
]
Rohith Sharma K S commented on YARN-5585:
-----------------------------------------
bq. Then the entity id order is really the earliest first. Is that what we
intended?
Given entities are sorted in ascending order, at some extent latest fist order
can be achieve by doing reverse scan. I had tried this for yarn-containers and
works fine.
bq. It would be the client's responsibility to ensure correct data gets in
Its not about entity data stored in but about number of extra rows get added in
HBase. Say one time user is published entities with prefix and on next time
user is published with different prefix or no-prefix for same entity. Since
there is not validation from server end for each entity updates, unnecessary
rows get added up for same entityId.
bq. Also note that we expect the AM to be the sole client for a given YARN app.
IIUC, AM can delegate collector address to any of its running containers to
publish its own data. TimelineClient can not be restricted to *only AM*.
> [Atsv2] Add a new filter fromId in REST endpoints
> -------------------------------------------------
>
> Key: YARN-5585
> URL: https://issues.apache.org/jira/browse/YARN-5585
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelinereader
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Priority: Critical
> Attachments: 0001-YARN-5585.patch, YARN-5585-workaround.patch,
> YARN-5585.v0.patch
>
>
> TimelineReader REST API's provides lot of filters to retrieve the
> applications. Along with those, it would be good to add new filter i.e fromId
> so that entities can be retrieved after the fromId.
> Current Behavior : Default limit is set to 100. If there are 1000 entities
> then REST call gives first/last 100 entities. How to retrieve next set of 100
> entities i.e 101 to 200 OR 900 to 801?
> Example : If applications are stored database, app-1 app-2 ... app-10.
> *getApps?limit=5* gives app-1 to app-5. But to retrieve next 5 apps, there is
> no way to achieve this.
> So proposal is to have fromId in the filter like
> *getApps?limit=5&&fromId=app-5* which gives list of apps from app-6 to
> app-10.
> Since ATS is targeting large number of entities storage, it is very common
> use case to get next set of entities using fromId rather than querying all
> the entites. This is very useful for pagination in web UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
