You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Created) (JIRA)" <ji...@apache.org> on 2012/03/26 19:40:28 UTC
[jira] [Created] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
make our launcher scripts recognize cascading defaults
------------------------------------------------------
Key: BIGTOP-492
URL: https://issues.apache.org/jira/browse/BIGTOP-492
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (BIGTOP-492) make our launcher
scripts recognize cascading defaults
Posted by "Roman Shaposhnik (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240088#comment-13240088 ]
Roman Shaposhnik edited comment on BIGTOP-492 at 3/28/12 1:14 AM:
------------------------------------------------------------------
Guys, this whole thing is *really* quite simple. Basically, here's what I propose to add to each of our launcher scripts *before* it execs the downstream script:
{noformat}
[ -e /etc/bigtop/<component name>rc ] && . /etc/bigtop/<component name>rc
[ -e ~/.bigtop/<component name>rc ] && . ~/.bigtop/<component name>rc
{noformat}
Nothing more, nothing less. Very, very simple stuff.
was (Author: rvs):
Guys, this whole thing is *really* quite simple. Basically, here's what I propose to add to each of our launcher scripts *before* it execs the downstream script:
{noformat}
[ -e /etc/bigtop/<component name>rc ] && . /etc/bigtop/<component name>rc
[ -e ~/.bigtop/<component name>rc ] && . /.bigtop/<component name>rc
{noformat}
Nothing more, nothing less. Very, very simple stuff.
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
Posted by "Roman Shaposhnik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238599#comment-13238599 ]
Roman Shaposhnik commented on BIGTOP-492:
-----------------------------------------
I'm not quite sure whether /etc/<util>rc or /etc/bigtop/<util>rc will be a better name for the system-level rc file for each component.
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (BIGTOP-492) make our launcher
scripts recognize cascading defaults
Posted by "Bruno Mahé (Issue Comment Edited JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238869#comment-13238869 ]
Bruno Mahé edited comment on BIGTOP-492 at 3/26/12 9:41 PM:
------------------------------------------------------------
* Could you give more details regarding how you see this being done?
* How are these scripts created? populated? read?
* How do you plan on educating users about this Apache Bigtop (incubating) specific feature?
* How more complicated will become debugging configurations issues?
* What are the benefits from a user point of view? Just avoiding exporting <COMPONENT>_CONF_DIR>, passing parameter -conf, overriding properties -D<something>, editing the files? Why use that when I can just points to another conf dir?
* How much complexity/layer of indirection will this feature add? Is the added value worthwhile?
Overall I am neutral provided this does not add too much confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value added. But Apache Bigtop (incubating) being a volunteer based project, anyone can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
was (Author: bmahe):
* Could you give more details regarding how you see this being done?
* How are these scripts created? populated? read?
* How do you plan on educating users about this Apache Bigtop (incubating) specific feature?
* How more complicated will debugging configurations issues will be?
* What are the benefits from a user point of view? Just avoiding exporting <COMPONENT>_CONF_DIR>, passing parameter -conf, overriding properties -D<something>, editing the files? Why use that when I can just points to another conf dir?
* How much complexity/layer of indirection will this feature add? Is the added value worthwhile?
Overall I am neutral provided this does not add too much confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value added. But Apache Bigtop (incubating) being a volunteer based project, anyone can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238869#comment-13238869 ]
Bruno Mahé commented on BIGTOP-492:
-----------------------------------
* Could you give more details regarding how you see this being done?
* How are these scripts created? populated? read?
* How do you plan on educating users about this Apache Bigtop (incubating) feature?
* How more complicated will debugging configurations issues will be?
* What are the benefits from a user point of view? Just avoiding exporting <COMPONENT>_CONF_DIR>, passing parameter -conf, overriding properties -D, editing the files? Why use that when I can just points to another conf dir?
* How much complexity/layer of indirection will this feature add? Is the added value worthwhile?
Overall I am neutral provided this does not add too much confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value added. But Apache Bigtop (incubating) being a volunteer based project, anyone can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240086#comment-13240086 ]
Bruno Mahé commented on BIGTOP-492:
-----------------------------------
But in any case users will have to know which variable to export/override, no?
What layer of abstraction are you thinking about? How much complexity will be added?
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (BIGTOP-492) make our launcher
scripts recognize cascading defaults
Posted by "Bruno Mahé (Issue Comment Edited JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238869#comment-13238869 ]
Bruno Mahé edited comment on BIGTOP-492 at 3/26/12 9:35 PM:
------------------------------------------------------------
* Could you give more details regarding how you see this being done?
* How are these scripts created? populated? read?
* How do you plan on educating users about this Apache Bigtop (incubating) specific feature?
* How more complicated will debugging configurations issues will be?
* What are the benefits from a user point of view? Just avoiding exporting <COMPONENT>_CONF_DIR>, passing parameter -conf, overriding properties -D<something>, editing the files? Why use that when I can just points to another conf dir?
* How much complexity/layer of indirection will this feature add? Is the added value worthwhile?
Overall I am neutral provided this does not add too much confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value added. But Apache Bigtop (incubating) being a volunteer based project, anyone can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
was (Author: bmahe):
* Could you give more details regarding how you see this being done?
* How are these scripts created? populated? read?
* How do you plan on educating users about this Apache Bigtop (incubating) specific feature?
* How more complicated will debugging configurations issues will be?
* What are the benefits from a user point of view? Just avoiding exporting <COMPONENT>_CONF_DIR>, passing parameter -conf, overriding properties -D, editing the files? Why use that when I can just points to another conf dir?
* How much complexity/layer of indirection will this feature add? Is the added value worthwhile?
Overall I am neutral provided this does not add too much confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value added. But Apache Bigtop (incubating) being a volunteer based project, anyone can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
Posted by "Roman Shaposhnik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240088#comment-13240088 ]
Roman Shaposhnik commented on BIGTOP-492:
-----------------------------------------
Guys, this whole thing is *really* quite simple. Basically, here's what I propose to add to each of our launcher scripts *before* it execs the downstream script:
{noformat}
[ -e /etc/bigtop/<component name>rc ] && . /etc/bigtop/<component name>rc
[ -e ~/.bigtop/<component name>rc ] && . /.bigtop/<component name>rc
{noformat}
Nothing more, nothing less. Very, very simple stuff.
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (BIGTOP-492) make our launcher
scripts recognize cascading defaults
Posted by "Bruno Mahé (Issue Comment Edited JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238869#comment-13238869 ]
Bruno Mahé edited comment on BIGTOP-492 at 3/26/12 9:34 PM:
------------------------------------------------------------
* Could you give more details regarding how you see this being done?
* How are these scripts created? populated? read?
* How do you plan on educating users about this Apache Bigtop (incubating) specific feature?
* How more complicated will debugging configurations issues will be?
* What are the benefits from a user point of view? Just avoiding exporting <COMPONENT>_CONF_DIR>, passing parameter -conf, overriding properties -D, editing the files? Why use that when I can just points to another conf dir?
* How much complexity/layer of indirection will this feature add? Is the added value worthwhile?
Overall I am neutral provided this does not add too much confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value added. But Apache Bigtop (incubating) being a volunteer based project, anyone can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
was (Author: bmahe):
* Could you give more details regarding how you see this being done?
* How are these scripts created? populated? read?
* How do you plan on educating users about this Apache Bigtop (incubating) feature?
* How more complicated will debugging configurations issues will be?
* What are the benefits from a user point of view? Just avoiding exporting <COMPONENT>_CONF_DIR>, passing parameter -conf, overriding properties -D, editing the files? Why use that when I can just points to another conf dir?
* How much complexity/layer of indirection will this feature add? Is the added value worthwhile?
Overall I am neutral provided this does not add too much confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value added. But Apache Bigtop (incubating) being a volunteer based project, anyone can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
Posted by "Roman Shaposhnik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238816#comment-13238816 ]
Roman Shaposhnik commented on BIGTOP-492:
-----------------------------------------
This is basically aimed at generalizing <foo>-env.sh. 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 *env.sh
The trouble with the current Hadoop ecosystem is that it is very developer-centric in its use of <foo>-env.sh:
# 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, hadoop-env.sh 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: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
Posted by "Roman Shaposhnik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240084#comment-13240084 ]
Roman Shaposhnik commented on BIGTOP-492:
-----------------------------------------
@Philip,
the goal here is consistency, I guess. I'm sure in every single Hadoop ecosystem component there's a way to achieve this goal of cascading defaults. They are all different though and difficult to remember. A proposed scheme has a nice advantage of regularizing this to a point where you can be sure of what exact shell environment all of the launcher scripts will be executed in.
As I mentioned, the downside is divergence from upstream.
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
Posted by "Philip Zeyliger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239812#comment-13239812 ]
Philip Zeyliger commented on BIGTOP-492:
----------------------------------------
Roman,
Seems like HADOOP_CONF_DIR already lets you override stuff; is that not enough?
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
cascading defaults
Posted by "Philip Zeyliger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238608#comment-13238608 ]
Philip Zeyliger commented on BIGTOP-492:
----------------------------------------
Is this to more easily support multiple Hadoop clusters on the same machine? Is it for the *xml files, the *env files, both?
I'm not clear what this issue is trying to fix. {{.my.cnf}}, something vaguely similar, lets you specify MySQL client configs, but Hadoop's configs are very mixed client/server.
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira