[
https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523904#comment-15523904
]
Li Lu commented on YARN-5585:
-----------------------------
Hi [~rohithsharma], some of my understandings
bq. IIUC from user perspective, while publishing entity, user need to provide
entityPrefixId in TimelineEntity object. If plan is to add new entityPrefixId
in as row key, and expecting to provide while publishing entity then why cant
createdTime itself used as row key? If createdTime is not provided, however
default sorting i.e lexicographical order will be returned.
This is doable, but providing a prefix field allows users to have more
flexibility to customize sorting orders. Users need only a single statement to
put created time or reverted created time into the prefix.
bq. Does there will be an default comparator for entityPrefixId in
TimelineEntity object?
We were discussing to completely rework on the compare methods of timeline
entities to provide a natural order that is consistent with our discussion
here. Thoughts?
> [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: 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: [email protected]
For additional commands, e-mail: [email protected]
