[
https://issues.apache.org/jira/browse/YUNIKORN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176781#comment-17176781
]
Wilfred Spiegelenburg commented on YUNIKORN-359:
------------------------------------------------
For the long term should we not use the partition name as a part of the URL?
Move the queues and all other partition based pieces to either
{{/ws/v1/<partition>/queues}} or {{/ws/v1/queues/<partition>}} I think the
first option is the correct one. And yes that would require far more changes.
Either solution needs a two step approach: get the list of partitions and
get/build the url to retrieve the per partition info.
BTW Not sure if using a query parameter is the right thing. There is really no
"default" partition. We use it in the configs everywhere but from a core
scheduler perspective it does not have to exist. So I am not sure that we can
really return a "default" if nothing has been set.
We would need something for all three partition unique objects: queues, nodes
and applications.
> Support for "queue" query param filter
> --------------------------------------
>
> Key: YUNIKORN-359
> URL: https://issues.apache.org/jira/browse/YUNIKORN-359
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
>
> Support "queue" query param filter to the following handlers:
>
> 1. /ws/v1/queues
> Return only queue info whose name exactly matches with "queue" query param
> 2. /ws/v1/nodes
> As of now, Each Node Info has all allocations made on that Node. With this
> change, it returns only Node info of Nodes whose allocation queue name
> exactly matches with "queue" query param. In effect, filter happens on
> allocations.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
