[
https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552438#comment-15552438
]
Sangjin Lee commented on YARN-5585:
-----------------------------------
bq. Entity IDs' can be anything. Even a completely alphabetical sequence can be
an entity ID. So it will not be possible to define a reverse order for every
generic entity ID. Is this your question ?
Yes, it was more of a realization on my part on how it behaves. For some
reason, I thought that we would return the most recent entities first (i.e.
reverse order of the entity id's). For example, if we had entity_0, entity_1,
..., entity_9, and queried with limit = 5, I had thought that we would return
entity_5 through entity_9. Now I realize we would return entity_0 through
entity_4 (that also explains some of Rohith's early comments). Then the entity
id order is really the earliest first. Is that what we intended? I know
"reversing" an arbitrary string is not easy, but I want to make sure if we're
on the same page and if there is a way to accomplish the most recent entity
order.
bq. Secondly, what if users misses providing an prefixId in subsequent updates.?
I agree with Varun on this. Even without the prefix, clients can set any value
for entities, and the storage will store them per schema. It would be the
client's responsibility to ensure correct data gets in. Also note that we
expect the AM to be the sole client for a given YARN app.
> [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
