[
https://issues.apache.org/jira/browse/YUNIKORN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176474#comment-17176474
]
Sunil G commented on YUNIKORN-359:
----------------------------------
??~From general intuition perspective, exposing any optional query param and in
case users don't pass any value, expected results should be across this param.
For ex, In case of non-empty "partition", search should be with in that
"partition" context. Otherwise, it should be across (in this case, across all
partitions). So, am not sure assuming "default/first" would be an intuitive
thing to do.~??
Based on the context of a partition or multiple partitions, we need to see the
use case of having such an aggregated value from YuniKorn. To me, aggregation
or slicing up etc is up to end consumer (a UI or webclient) for many partitions
together. Hence if there are no specific partition is not asked, we may need to
go for the default one.
??When we read endpoint as "clusters", as a user, would expectation be
something about overall summary/picture of a cluster rather than partition wise
info? Here, we are having 1 cluster, no concept of multiple clusters.??
Good point. We can reshuffle some of partition data from cluster. However
cluster still need to have some higher level infromations.
??{{var clustersInfo []dao.ClusterDAOInfo}} is initialising and overriding
previous partition results every time.??
If its an array, it should ideally append.
I have some test case to cover this, will share same so that some of this can
be shown with more clarity.
> 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]
