Kai Sasaki commented on YARN-5145:

Sorry for lacking of explanation. It seems that {{configs.env}} is not used 
anymore because all configurations are included in {{default-config.js}}. And 
new YARN UI is working fine without {{configs.env}}. So we can remove this file.

And then after removing {{configs.env}} file, there is no {{config}} directory 
under {{$HADOOP_PREFIX/share/hadoop/yarn/webapps/}} because condifurations 
{{default-config.js}} are build into ember deploy. There is no configurations 
to be passed externally since they are included in ember deploy package.

So removing {{configs.env}} is intended to 
1. Since {{configs.env}} is not used anymore, it can be removed.
2. By removing config directory in ember deployed package, we found there is no 
configurations to be passed from external.

Does it make sense? 
But if any other new configurations are introduced which should be changed from 
external, we need to implement a way to pass some values to deployed ember 
package. Do you consider of such future usage?

> [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
> -------------------------------------------------------------
>                 Key: YARN-5145
>                 URL: https://issues.apache.org/jira/browse/YARN-5145
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Wangda Tan
>            Assignee: Kai Sasaki
>         Attachments: YARN-5145-YARN-3368.01.patch
> Existing YARN UI configuration is under Hadoop package's directory: 
> $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to 
> $HADOOP_CONF_DIR like other configurations.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to