[
https://issues.apache.org/jira/browse/STORM-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980180#comment-13980180
]
ASF GitHub Bot commented on STORM-295:
--------------------------------------
Github user sureshms commented on the pull request:
https://github.com/apache/incubator-storm/pull/85#issuecomment-41324906
The problem with the approach you are talking about is, the shell where
STORM services are started, STORM_JAVA_HOME should be set. Having storm_env.sh,
some what similar hadoop_env.sh could be a nice way to capture configuration
and use it in the scripts. I can certainly turn storm_env.sh into an ini file
and directly use it in python, instead of using shell script that uses
storm_env.sh to launch python script. What do you think?
> Add storm configuration to define JAVA_HOME
> -------------------------------------------
>
> Key: STORM-295
> URL: https://issues.apache.org/jira/browse/STORM-295
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Reporter: Suresh Srinivas
>
> Currently storm uses either /usr/bin/java (most likely) or java pointed to by
> PATH.
> Storm requires a way to define JAVA_HOME in configuration. This will simplify
> pointing to a version of java that a cluster admin or test frameworks intend
> to use for storm, especially in an environments where multiple versions of
> java is on the cluster nodes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
