[
https://issues.apache.org/jira/browse/OOZIE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382661#comment-14382661
]
Harsh J commented on OOZIE-2185:
--------------------------------
Using a client-specific file (oozie-client-env.sh) sounds fine to me. Would you
have some time to contribute this change Robert? We can set the default source
location to /etc/oozie/conf, but otherwise pick via env-var
OOZIE_CLIENT_CONF_DIR, and ignore failures/logic-steps if no such path is found.
> 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.0.1
> Reporter: Robert Justice
> Priority: Minor
> Labels: feature, newbie
>
> 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)
