[
https://issues.apache.org/jira/browse/OOZIE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027683#comment-15027683
]
Robert Kanter commented on OOZIE-2185:
--------------------------------------
I'll need to spend a bit more time playing around with it; probably some time
next week. But at a first glance, this seems reasonable. A few minor things:
# Most users won't need to set {{OOZIE_AUTH}} explicitly because the Oozie
Client figures this out automatically most of the time. I think we should
mention that in the description; something like:
{noformat}
# Authenticaton type - used as value for the '-auth' option if set
# Note that Oozie normally determines this automatically so you usually won't
need to set it
# Options: [SIMPLE|KERBEROS]
{noformat}
# Missing a newline at the end of oozie-client-env.sh
# It would be good to also put {{OOZIE_CLIENT_OPTS}} in there (it lets you
apply JVM options, such as Xmx, truststore, etc)
> 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
> Assignee: Mike Grimes
> 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)
