[
https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817675#comment-15817675
]
Rohith Sharma K S commented on YARN-6027:
-----------------------------------------
bq. Is that making things slow?
Yes, it is slow
bq. Should we consider aggregating at the server side before returning data?
That way, the amount of data returned is less.
Yup, this what we really looking. Given a date range, Flow collapse would be
better and also pagination will be easier for collapsed flows. Importantly,
collapsed flows retrieval should be fixed(we can define new limit), and this
can not be same as limit.
> Support fromId for flows API
> -----------------------------
>
> Key: YARN-6027
> URL: https://issues.apache.org/jira/browse/YARN-6027
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Labels: yarn-5355-merge-blocker
>
> In YARN-5585 , fromId is supported for retrieving entities. We need similar
> filter for flows/flowRun apps and flow run and flow as well.
> Along with supporting fromId, this JIRA should also discuss following points
> * Should we throw an exception for entities/entity retrieval if duplicates
> found?
> * TimelieEntity :
> ** Should equals method also check for idPrefix?
> ** Does idPrefix is part of identifiers?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
