[jira] [Updated] (HADOOP-9642) Configuration to resolve environment variables via ${env.VARIABLE} references
[ https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-9642: - Issue Type: New Feature (was: Improvement) Configuration to resolve environment variables via ${env.VARIABLE} references - Key: HADOOP-9642 URL: https://issues.apache.org/jira/browse/HADOOP-9642 Project: Hadoop Common Issue Type: New Feature Components: conf, scripts Affects Versions: 3.0.0, 2.1.0-beta Reporter: Steve Loughran Assignee: Kengo Seki Priority: Minor Attachments: HADOOP-9642.001.patch, HADOOP-9642.002.patch We should be able to get env variables from Configuration files, rather than just system properties. I propose using the traditional {{env}} prefix {{${env.PATH}}} to make it immediately clear to people reading a conf file that it's an env variable -and to avoid any confusion with system properties and existing configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-9642) Configuration to resolve environment variables via ${env.VARIABLE} references
[ https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-9642: - Resolution: Fixed Fix Version/s: 3.0.0 Status: Resolved (was: Patch Available) +1 lgtm. committed to trunk. Thanks! Configuration to resolve environment variables via ${env.VARIABLE} references - Key: HADOOP-9642 URL: https://issues.apache.org/jira/browse/HADOOP-9642 Project: Hadoop Common Issue Type: New Feature Components: conf, scripts Affects Versions: 3.0.0, 2.1.0-beta Reporter: Steve Loughran Assignee: Kengo Seki Priority: Minor Fix For: 3.0.0 Attachments: HADOOP-9642.001.patch, HADOOP-9642.002.patch We should be able to get env variables from Configuration files, rather than just system properties. I propose using the traditional {{env}} prefix {{${env.PATH}}} to make it immediately clear to people reading a conf file that it's an env variable -and to avoid any confusion with system properties and existing configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-9642) Configuration to resolve environment variables via ${env.VARIABLE} references
[ https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kengo Seki updated HADOOP-9642: --- Attachment: HADOOP-9642.002.patch Attaching a revised patch. - Default value feature added. In addition to :\-, - is also supported. - Javadoc modified. Could anyone review it? Thank you. Configuration to resolve environment variables via ${env.VARIABLE} references - Key: HADOOP-9642 URL: https://issues.apache.org/jira/browse/HADOOP-9642 Project: Hadoop Common Issue Type: Improvement Components: conf, scripts Affects Versions: 3.0.0, 2.1.0-beta Reporter: Steve Loughran Assignee: Kengo Seki Priority: Minor Attachments: HADOOP-9642.001.patch, HADOOP-9642.002.patch We should be able to get env variables from Configuration files, rather than just system properties. I propose using the traditional {{env}} prefix {{${env.PATH}}} to make it immediately clear to people reading a conf file that it's an env variable -and to avoid any confusion with system properties and existing configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-9642) Configuration to resolve environment variables via ${env.VARIABLE} references
[ https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kengo Seki updated HADOOP-9642: --- Status: Patch Available (was: Open) Configuration to resolve environment variables via ${env.VARIABLE} references - Key: HADOOP-9642 URL: https://issues.apache.org/jira/browse/HADOOP-9642 Project: Hadoop Common Issue Type: Improvement Components: conf, scripts Affects Versions: 2.1.0-beta, 3.0.0 Reporter: Steve Loughran Priority: Minor Attachments: HADOOP-9642.001.patch We should be able to get env variables from Configuration files, rather than just system properties. I propose using the traditional {{env}} prefix {{${env.PATH}}} to make it immediately clear to people reading a conf file that it's an env variable -and to avoid any confusion with system properties and existing configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-9642) Configuration to resolve environment variables via ${env.VARIABLE} references
[ https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kengo Seki updated HADOOP-9642: --- Attachment: HADOOP-9642.001.patch Attaching a preliminary patch. Default values are not supported yet. Configuration to resolve environment variables via ${env.VARIABLE} references - Key: HADOOP-9642 URL: https://issues.apache.org/jira/browse/HADOOP-9642 Project: Hadoop Common Issue Type: Improvement Components: conf, scripts Affects Versions: 3.0.0, 2.1.0-beta Reporter: Steve Loughran Priority: Minor Attachments: HADOOP-9642.001.patch We should be able to get env variables from Configuration files, rather than just system properties. I propose using the traditional {{env}} prefix {{${env.PATH}}} to make it immediately clear to people reading a conf file that it's an env variable -and to avoid any confusion with system properties and existing configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-9642) Configuration to resolve environment variables via ${env.VARIABLE} references
[ https://issues.apache.org/jira/browse/HADOOP-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HADOOP-9642: - Component/s: scripts Configuration to resolve environment variables via ${env.VARIABLE} references - Key: HADOOP-9642 URL: https://issues.apache.org/jira/browse/HADOOP-9642 Project: Hadoop Common Issue Type: Improvement Components: conf, scripts Affects Versions: 3.0.0, 2.1.0-beta Reporter: Steve Loughran Priority: Minor We should be able to get env variables from Configuration files, rather than just system properties. I propose using the traditional {{env}} prefix {{${env.PATH}}} to make it immediately clear to people reading a conf file that it's an env variable -and to avoid any confusion with system properties and existing configuration properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)