[
https://issues.apache.org/jira/browse/YARN-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200987#comment-16200987
]
Jason Lowe commented on YARN-7286:
----------------------------------
I suspect the behavior difference stems from the different handling of
properties loaded from site XML files vs. programmatically set properties. The
former are treated as resources while the latter are set in the property and
overlay collections directly. When loading resources it ignores null values
for properties unless setAllowNullValueProperties is set, which nothing but
test code does. I don't think it's safe to change that behavior at this point
since it's always behaved that way. Configuration is one of those "everybody
uses it and has learned to live with its bugs/quirks" things. Changing its
existing behavior is likely to break some downstream project, e.g.: if we were
to make final fields _really_ final even if programmatically set.
> Add support for docker to have no capabilities
> ----------------------------------------------
>
> Key: YARN-7286
> URL: https://issues.apache.org/jira/browse/YARN-7286
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Eric Badger
> Assignee: Eric Badger
> Attachments: YARN-7286.001.patch, YARN-7286.002.patch,
> YARN-7286.003.patch
>
>
> Support for controlling capabilities was introduced in YARN-4258. However, it
> does not allow for the capabilities list to be NULL, since {{getStrings()}}
> will treat an empty value the same as it treats an unset property. So, a NULL
> list will actually give the default capabilities list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
