[
https://issues.apache.org/jira/browse/YUNIKORN-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247070#comment-17247070
]
Manikandan R commented on YUNIKORN-418:
---------------------------------------
As of now, config REST API supports two methods: 1. GET to get the config. 2.
PUT to update the config.
At a high level, Like other sub jira's in YUNIKORN-418 umbrella jira, this API
doesn't require major redesign (as documented) etc except few things listed
below:
1. Scope of "config" API is at cluster object level. Change in config could be
at partition, queue level etc. But, when it comes to update, we are passing the
entire new configuration for change. If required, may be can rename url from
"v1/config" to "v1/cluster/config". However, leaving the url as is also fine as
I don't think that we would be supporting partition, queue etc specific config
changes exclusively through objects specific API's ( for ex,
partition/{default}/config etc )
2. It is good to merge "validate-conf" API with "config" API. Exposing query
param like "dry_run" (default is 0) in "config" API (PUT method) itself can
take care of validation as anyways config#LoadSchedulerConfigFromByteArray()
call happens in handlers#updateConfig() method.
[~wilfreds][~sunilg] [~cheersyang] Thoughts?
> Add "config" REST API
> ---------------------
>
> Key: YUNIKORN-418
> URL: https://issues.apache.org/jira/browse/YUNIKORN-418
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
