[ https://issues.apache.org/jira/browse/YARN-9593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853546#comment-16853546 ]
Anthony Hsu commented on YARN-9593: ----------------------------------- Hi [~jhung], Thanks for sharing the workaround. That works for me for now. I think the CLI can be updated to ignore escaped commas ({{\,}}) to support confs with commas (which can escape the commas). How does that sound to you? > Updating scheduler conf with comma in config value fails > -------------------------------------------------------- > > Key: YARN-9593 > URL: https://issues.apache.org/jira/browse/YARN-9593 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 2.9.0, 3.0.0, 3.2.0, 3.1.2 > Reporter: Anthony Hsu > Priority: Major > > For example: > {code:java} > $ yarn schedulerconf -update "root.gridops:acl_administer_queue=user1,user2 > group1,group2" > Specify configuration key value as confKey=confVal.{code} > This fails because there is a comma in the config value and the SchedConfCLI > splits on comma first, expecting each split to a k=v pair. > {noformat} > void globalUpdates(String args, SchedConfUpdateInfo updateInfo) { > if (args == null) { > return; > } > HashMap<String, String> globalUpdates = new HashMap<>(); > for (String globalUpdate : args.split(",")) { > putKeyValuePair(globalUpdates, globalUpdate); > } > updateInfo.setGlobalParams(globalUpdates); > }{noformat} > Cc: [~jhung] -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org