[ https://issues.apache.org/jira/browse/YARN-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201121#comment-16201121 ]
Sidharta Seethana commented on YARN-7286: ----------------------------------------- Agreed, we shouldn't be changing that behavior at this point. I am ok with the "NONE" approach. With respect to mixing "NONE" and other capabilities, how about moving capability configuration handling to the initialization function in {{DockerLinuxContainerRuntime}} and throw an exception there in case they are mixed? It should probably have been in that function in the first place - all other config handling is in that function. > 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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org