[
https://issues.apache.org/jira/browse/YUNIKORN-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777864#comment-17777864
]
Craig Condit commented on YUNIKORN-2061:
----------------------------------------
I'm very much *not* in favor of this change. Adding pagination implies
unchanging state, ordering, and consistency between calls, none of which is
actually true in reality. This will result in a brittle, error-prone interface.
Additionally, this adds additional load to the scheduler, which we don't want
to introduce. Finally, none of these APIs should ever be unreasonably large for
an API (i.e. millions of records).
> [Umbrella] Add Pagination to APIs which may have lot of items in response
> -------------------------------------------------------------------------
>
> Key: YUNIKORN-2061
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2061
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - common, webapp
> Reporter: PoAn Yang
> Assignee: JiaChi Wang
> Priority: Major
>
> The following API may have lot of items in one response. It's good to add
> pagination design to them.
> * Queue applications
> (/ws/v1/partition/\{partitionName}/queue/\{queueName}/applications)
> * Application history (/ws/v1/history/apps)
> * Container history (/ws/v1/history/containers)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
