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 07:15:09 UTC
[jira] [Created] (OOZIE-310) GH-482: coordinator default config is
looked up in the wrong place (regression)
GH-482: coordinator default config is looked up in the wrong place (regression)
-------------------------------------------------------------------------------
Key: OOZIE-310
URL: https://issues.apache.org/jira/browse/OOZIE-310
Project: Oozie
Issue Type: Bug
Reporter: Hadoop QA
The config defaults should be looked in the coord-app directory.
Currently it is looked in the wrong location. For example:
hdfs://localhost:9000/user/tucu/examples/apps/cron/coordinator.xml/coord-config-default.xml
This seems a regression introduced with implicit coordinator.xml resolution.
Furthermore with latest version of Hadoop a check for existence of a file as the example above gives an exception, it seems that now Hadoop looks for the parent to exist.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-310) GH-482: coordinator default config
is looked up in the wrong place (regression)
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099982#comment-13099982 ]
Hadoop QA commented on OOZIE-310:
---------------------------------
tucu00 remarked:
Closed by ce428e55a36c3ee6a1f6d9a5abad9252b015ed85 coordinator default config is looked up in the wrong place (regression)
> GH-482: coordinator default config is looked up in the wrong place (regression)
> -------------------------------------------------------------------------------
>
> Key: OOZIE-310
> URL: https://issues.apache.org/jira/browse/OOZIE-310
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> The config defaults should be looked in the coord-app directory.
> Currently it is looked in the wrong location. For example:
> hdfs://localhost:9000/user/tucu/examples/apps/cron/coordinator.xml/coord-config-default.xml
> This seems a regression introduced with implicit coordinator.xml resolution.
> Furthermore with latest version of Hadoop a check for existence of a file as the example above gives an exception, it seems that now Hadoop looks for the parent to exist.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OOZIE-310) GH-482: coordinator default config is
looked up in the wrong place (regression)
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik closed OOZIE-310.
----------------------------------
Resolution: Fixed
> GH-482: coordinator default config is looked up in the wrong place (regression)
> -------------------------------------------------------------------------------
>
> Key: OOZIE-310
> URL: https://issues.apache.org/jira/browse/OOZIE-310
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> The config defaults should be looked in the coord-app directory.
> Currently it is looked in the wrong location. For example:
> hdfs://localhost:9000/user/tucu/examples/apps/cron/coordinator.xml/coord-config-default.xml
> This seems a regression introduced with implicit coordinator.xml resolution.
> Furthermore with latest version of Hadoop a check for existence of a file as the example above gives an exception, it seems that now Hadoop looks for the parent to exist.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira