You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/09 03:01:27 UTC
[jira] [Updated] (STORM-160) Allow ShellBolt to set env vars
(particularly PATH)
[ https://issues.apache.org/jira/browse/STORM-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Kellogg updated STORM-160:
-------------------------------
Component/s: storm-multilang
> Allow ShellBolt to set env vars (particularly PATH)
> ---------------------------------------------------
>
> Key: STORM-160
> URL: https://issues.apache.org/jira/browse/STORM-160
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-multilang
> Reporter: James Xu
> Assignee: Shyam Rajendran
> Priority: Minor
> Labels: newbie
> Fix For: 0.11.0
>
>
> https://github.com/nathanmarz/storm/issues/32
> While trying to implement a multilang based bolt, I discovered that binaries outside of /usr/bin, /usr/sbin, and /sbin, are not found despite being installed in say, /usr/local/bin.
> Is there a way to specify a PATH variable so when storm creates the sub shell, these binaries can be located by name? If not, can we get one added?
> ----------
> nathanmarz: This is a good idea. For the meantime, does using the full path of the binary (e.g., /usr/local/bin/python) work around this issue?
> ----------
> dinedal: That works for processes that don't require any other environment variables.
> Also, in cases where developers have multiple versions of a program (say, RVM) and the production servers have another one installed on the system, it means changing code for deploying the topology.
> ----------
> nicoo: +1
> To work around this issue you can start your multilang bolt from a bash script that set all needed env vars.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)