[jira] [Updated] (BIGTOP-1037) Provide a mechanism to control the sourcing of defaults files

["Sean Mackrory (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BIGTOP-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory updated BIGTOP-1037:
----------------------------------

    Attachment: 0001-BIGTOP-1037.-Provide-a-mechanism-to-control-the-sour.patch

That is probably wise - thanks, Bruno. Updated the patch...
                
> Provide a mechanism to control the sourcing of defaults files
> -------------------------------------------------------------
>
>                 Key: BIGTOP-1037
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1037
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>         Attachments: 0001-BIGTOP-1037.-Provide-a-mechanism-to-control-the-sour.patch, 0001-BIGTOP-1037.-Provide-a-mechanism-to-control-the-sour.patch
>
>
> Ideally, defaults files should only contain name / value pairs (as per Debian packaging policy), which makes it difficult for a cluster management system that may be managing Hadoop to control the environment when these files are sources and variables are perhaps exported into the environment unconditionally.
> In keeping with Bigtop's goal if integrating Hadoop with the underlying operating system, the default behavior should not change *at all*, but it would provide greater flexibility if there was a mechanism to disable the sourcing of files so that if a system wants the environment variables to be used exclusively, the defaults files won't override that behavior.
> Obviously since this may be a more rare use case right now, the solution should also be as safe and non-disruptive as possible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira