You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Mike Grimes (JIRA)" <ji...@apache.org> on 2015/11/20 19:37:11 UTC

[jira] [Updated] (OOZIE-2185) Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)

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

Mike Grimes updated OOZIE-2185:
-------------------------------
    Attachment: OOZIE-2185-1.patch

> Make oozie cli source /etc/oozie/conf/oozie-env.sh (or some other env script)
> -----------------------------------------------------------------------------
>
>                 Key: OOZIE-2185
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2185
>             Project: Oozie
>          Issue Type: New Feature
>          Components: client
>    Affects Versions: 4.2.0
>            Reporter: Robert Justice
>            Priority: Minor
>              Labels: client, feature, newbie
>         Attachments: OOZIE-2185-1.patch
>
>
> Currently, the oozie cli doesn't source any environment script.   Users may wish to define environment variables such as OOZIE_URL outside of normal shell environment and have the oozie cli source /etc/oozie/conf/oozie-env.sh.  This is somewhat confusing when users see hadoop commands sourcing hadoop-env.sh, mapred-env.sh, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)