[
https://issues.apache.org/jira/browse/YUNIKORN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185893#comment-17185893
]
Manikandan R commented on YUNIKORN-359:
---------------------------------------
Thanks for the update.
Updated the doc as well.
Will delete (as won't do) subtasks created under
https://issues.apache.org/jira/browse/YUNIKORN-283 as we changed the entire
approach itself. Also will create a new umbrella Jira and create subtasks for
all 4 api's described in the document and start working on the implementation.
Are we good with this plan? Yes, we will keep in sync with [~akhilpb] for UI
changes.
> 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]
