You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Eric Badger (JIRA)" <ji...@apache.org> on 2017/10/04 16:31:00 UTC
[jira] [Updated] (YARN-7286) Add support for docker to have no
capabilities
[ https://issues.apache.org/jira/browse/YARN-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Badger updated YARN-7286:
------------------------------
Attachment: YARN-7286.001.patch
Attaching patch that utilizes the keyword "none" to remove force no capabilities to be added. This keyword supersedes anything else in the capabilities list. I was going to have it throw an error on a list with the "none" keyword and with extra capabilities, but the function doesn't expect an exception and I didn't want to change a bunch of function signatures. However, if that is best I can update the patch to do so.
> 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
>
>
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org