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] [Created] (OOZIE-172) GH-168: Being able to read Oozie
configuration for an arbitrary directory
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
[jira] [Commented] (OOZIE-172) GH-168: Being able to read Oozie
configuration for an arbitrary directory
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099858#comment-13099858 ]
Hadoop QA commented on OOZIE-172:
---------------------------------
tucu00 remarked:
Closed by ef696a26165bc68e1703c3ee2921623d3d09cffb Being able to read Oozie configuration for an arbitrary directory
Configuration is read from ${OOZIE_CONFIG_DIR} directory.
If the ENV var OOZIE_CONFIG_DIR is not defined, configuration is read from ${OOZIE_HOME}/conf
> 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
[jira] [Closed] (OOZIE-172) GH-168: Being able to read Oozie
configuration for an arbitrary directory
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ 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