You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:45:09 UTC
[jira] [Commented] (OOZIE-170) GH-165: oozie-start.sh should source
${OOZIE_HOME}/conf/oozie-env.sh
[ https://issues.apache.org/jira/browse/OOZIE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099856#comment-13099856 ]
Hadoop QA commented on OOZIE-170:
---------------------------------
tucu00 remarked:
Closed by 54069a7afd3c0f4c65d8ba65aa231ad2014888a7 oozie-start.sh should source ${OOZIE_HOME}/conf/oozie-env.sh
Added oozie-env.sh to conf/ directory.
Modified oozie-start.sh to source it.
Formatted a bit startup echo messages.
> GH-165: oozie-start.sh should source ${OOZIE_HOME}/conf/oozie-env.sh
> --------------------------------------------------------------------
>
> Key: OOZIE-170
> URL: https://issues.apache.org/jira/browse/OOZIE-170
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> This issue depends on GH-0131
> This will enable setting the environment by configuration (similar to what Hadoop does for its daemons).
> oozie-env.sh could be used to set the OOZIE_HTTP_PORT, OOZIE_HTTP_HOSTNAME and/or Tomcat settings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira