You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2018/09/13 14:07:00 UTC
[jira] [Resolved] (AMBARI-24633) Ambari strips leading space for
valid YARN configs on the config compare screen
[ https://issues.apache.org/jira/browse/AMBARI-24633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonenko Alexander resolved AMBARI-24633.
------------------------------------------
Resolution: Fixed
Committed to trunk and branch-2.6
> Ambari strips leading space for valid YARN configs on the config compare screen
> -------------------------------------------------------------------------------
>
> Key: AMBARI-24633
> URL: https://issues.apache.org/jira/browse/AMBARI-24633
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.7.1
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 2 optional properties in yarn-site,
> {noformat}
> yarn.timeline-service.read.allowed.users
> <queue>.acl_application_max_priority
> {noformat}
> are of the form
> {noformat}
> <user1>,<user2>..<white_space><group1>,<group2>..
> {noformat}
> Here the users are optional. Hence only groups could be specified with a leading space followed by <group1>,<group2>..
> But after setting such a configuration, Ambari strips the leading space and shows them as
> {noformat}
> <group1>,<group2>
> {noformat}
> instead of,
> {noformat}
> <group1>,<group2>
> {noformat}
> when comparing 2 config versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)