[
https://issues.apache.org/jira/browse/YUNIKORN-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199679#comment-17199679
]
Weiwei Yang commented on YUNIKORN-335:
--------------------------------------
Thanks [~kmarton] for working on this.
Since we are adding more validations, could we cover the following cases such
as:
* multiple queues in the first level
* having upper case letters in queue names
> Invalid config validation and config schema checks for unsupported config
> properties
> ------------------------------------------------------------------------------------
>
> Key: YUNIKORN-335
> URL: https://issues.apache.org/jira/browse/YUNIKORN-335
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
> Reporter: Ayub Pathan
> Assignee: Kinga Marton
> Priority: Major
> Labels: pull-request-available
>
> * Invalid configuration does not error out - accepts silently but does not
> reload the config.
> 4 spaces & 2 spaces - we should error out if 2 spaces is the standard.
> partitions:
> {noformat}
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> properties:
> application.sort.policy: stateaware{noformat}
> * Any unsupported configuration should not be allowed in the policy map -
> some kind of schema check is needed.
> {noformat}
> partitions:
> -
> name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> sample: value1
> properties:
> application.sort.policy: stateaware
> sample: value2{noformat}
>
> *Impact: User thinks the config is loaded and consumed by Yunikorn but its
> acutally not. So its important to error out incase any formatting issues.*
> [~wilfreds]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
