[
https://issues.apache.org/jira/browse/YUNIKORN-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798435#comment-17798435
]
Manikandan R commented on YUNIKORN-2235:
----------------------------------------
{quote}If the iteration cost is acceptable now, is there room to add more
queries in the future? Also, as a user I may expect it accepts other queries (
user, group, queue, and so on).
{quote}
As mentioned earlier, these 3 different types of apps are being stored in
different maps. Please see partition.go for more details. So, I don't think
there is much additional cost involved here. Also, I don't see a need for
other in near future. Even such need arises, we can extend User and Group api
response to cover the same. Current requirement is to display these 3 different
states of app in UI.
{quote}It seems that return these temporary state like expired, starting,
completing... is meaningless.
{quote}
As we all know Yunikorn is stateless. We can expose data available only at the
current moment. App moves from one state to another at different point in time.
So, we can expose data available at any particular moment. If there is a need
even to look at the historical data, then there is an [Application History
|https://yunikorn.apache.org/docs/api/scheduler/#application-history]option.
> Add new RESTful API for retrieving application
> ----------------------------------------------
>
> Key: YUNIKORN-2235
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2235
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: core - scheduler
> Reporter: Xie YiFan
> Assignee: Xie YiFan
> Priority: Minor
> Labels: pull-request-available
>
> *Situation:*
> Currently, the path format of retrieving application is
> /ws/v1/partition/\{partitionName}/queue/\{queueName}/application/\{appId}.
> We have to give 3 parameters (partitionName, queueName & appID) to fetch
> application information. But one application can only be submitted to one
> queue and PartitionContext stores all applications. It means that we can
> fetch the target application without queue name.
> *Proposal:*
> As we have discussed in slack, we can add the following 2 RESTful API.
> # /ws/v1/partition/\{partitionName}/applications/\{type}
> aim to list applications IDs via the types: rejected, running and completed
> # /ws/v1/partition/\{partitionName}/application/\{applicationID}
> aim to retrieving one application object directly.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
