You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2011/09/10 05:27:10 UTC
[jira] [Closed] (OOZIE-172) GH-168: Being able to read Oozie
configuration for an arbitrary directory
[ https://issues.apache.org/jira/browse/OOZIE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik closed OOZIE-172.
----------------------------------
Resolution: Fixed
> GH-168: Being able to read Oozie configuration for an arbitrary directory
> -------------------------------------------------------------------------
>
> Key: OOZIE-172
> URL: https://issues.apache.org/jira/browse/OOZIE-172
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Currently Oozie configuration is read from ${OOZIE_HOME}/conf/
> When deploying Oozie via native packages (RPM/DEB, CDH does this) the standard Unix filesystem layout is followed for conf/log/binaries/data.
> Because of this it should be possible to read Oozie configuration from /etc/oozie/
> This change should be done keeping the current behavior, ${OOZIE_HOME}/conf/ as the default.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira