[
https://issues.apache.org/jira/browse/YUNIKORN-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204831#comment-17204831
]
Kinga Marton commented on YUNIKORN-335:
---------------------------------------
[~wwei] I added upper case letter validation for the queue names. Not only
lower case letters are accepted.
Related the multiple queue issue, we agreed that actually that is the expected,
documented behaviour.
> 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]
