[
https://issues.apache.org/jira/browse/YUNIKORN-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363731#comment-17363731
]
Weiwei Yang commented on YUNIKORN-413:
--------------------------------------
{quote}
Even if we don't change the UI for the next release, I think we should keep it
open and target itt for one of the next releases. It would be good to reflect
the new API changes in the UI as well.
{quote}
If we retain the old APIs, why we need to change the UI code?
Unless we want to introduce a new UI workflow, e.g partition -> queue -> app.
[~kmarton] could you please elaborate on what is needed?
{quote}
Should we create a new jira to remove "deprecated" ?
{quote}
Yes, we need a JIRA for this. Not just remove "deprecated" word, we need to
format the doc a bit as well.
> [Umbrella] Re-designing Yunikorn REST API's version 1
> -----------------------------------------------------
>
> Key: YUNIKORN-413
> URL: https://issues.apache.org/jira/browse/YUNIKORN-413
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Critical
> Fix For: 0.11
>
>
> Scope of this umbrella Jira is to do redesigning all available REST API's and
> its corresponding UI changes based on the following thoughts:
> # Designing API based on objects hierarchy: Partitions->Queues->Applications.
> # Support for several query params.
> # Restructuring JSON response
> Design doc is available at
> [https://docs.google.com/document/d/1KgoGqmNGR7TK3yBeqmefiFso2_lQujA_TzlsU0SsG1o/edit?usp=sharing]
> Note: Initial discussion started at
> https://issues.apache.org/jira/browse/YUNIKORN-359. Please refer the same for
> background details.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
