[
https://issues.apache.org/jira/browse/OOZIE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022743#comment-15022743
]
Mike Grimes commented on OOZIE-2185:
------------------------------------
There really isn't any tests in place for these client scripts, so I didn't
feel it was necessary to add them (also not sure where best place for these
would be, if appropriate at all). Failed tests are unrelated and I think they
were failing my patch anyways.
> 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.3.0
> Reporter: Robert Justice
> Priority: Minor
> Labels: client, feature, newbie
> Attachments: OOZIE-2185-1.patch, OOZIE-2185-2.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)
