[ 
https://issues.apache.org/jira/browse/YUNIKORN-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363661#comment-17363661
 ] 

Manikandan R commented on YUNIKORN-413:
---------------------------------------

I also had the same thought. I was thinking of creating new umbrella jira as 
Phase 2 and move all these UI jiras with appropriate versions. REST API doc 
changes has been already made to mark the old API's as deprecated. Should we 
create a new jira to remove "deprecated" ?

> [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]

Reply via email to