incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (Commented) (JIRA)" <>
Subject [jira] [Commented] (BIGTOP-492) make our launcher scripts recognize cascading defaults
Date Mon, 26 Mar 2012 20:56:33 GMT


Roman Shaposhnik commented on BIGTOP-492:

This is basically aimed at generalizing <foo> It can be used for having a single
client for multiple clusters or anything else where you might want to have a system-level
defaults and then
user-level ones. It is NOT explicitly for *xml. It is a replacement/augmentation for *

The trouble with the current Hadoop ecosystem is that it is very developer-centric in its
use of <foo>
  # this script must come from the HOME of the component and not system-level location
  # this script doesn't allow for a second level of defaults 

Essentially, if you want to override things in, lets say, you can only do it
at a system-level leaving the user to use .bashrc for user-level overrides. That's the core
issue this JIRA is trying to address.
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>                 Key: BIGTOP-492
>                 URL:
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
> Almost all Unix (POSIX?) command line utilities have a nice feature of recognizing cascading
defaults. The system-level one is typically named /etc/<util>rc and the user-level one
is typically picked from ~/.<util>rc
> I propose that we introduce the same for all of the /usr/bin launcher scripts that we
support in Bigtop. The proposed format of the rc files is that of POSIX-compatible sh(1) code
snippet with an overall effect of exporting those variables that affect execution.
> Thoughts?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message