You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Shaik Idris Ali (Created) (JIRA)" <ji...@apache.org> on 2011/12/08 05:47:39 UTC
[jira] [Created] (OOZIE-630) Oozie coordinator error message
misleading
Oozie coordinator error message misleading
------------------------------------------
Key: OOZIE-630
URL: https://issues.apache.org/jira/browse/OOZIE-630
Project: Oozie
Issue Type: Bug
Environment: CDH3U0, Oozie 3.0.2, Pig 8.
Reporter: Shaik Idris Ali
Priority: Minor
My coordinator.xml has entry :
(under datasets)
<dataset name="impression-logs" frequency="${coord:minutes(20)}" initial-instance="2011-12-06T02:00Z" timezone="UTC">
<uri-template>${nameNode}/user/${coord:user()}/airavat/input/HourlyImpSummary/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}/0</uri-template>
<done-flag></done-flag>
</dataset>
and (under input-events)
<data-in name="impressionInputEvent" dataset="impression-logs">
<start-instance>${coord:current(-2)}</start-instance>
<end-instance>${coord:current(0)}</end-instance>
</data-in>
and (under workflow->configuration)
<property>
<name>impInputData</name>
<value>${coord:dataIn('impressionInputEvent')}</value>
</property>
The initial-instance="2011-12-06T11:00Z" does not exist. In fact it was a typo mistake from my side where I wanted the initial instance to be initial-instance="2011-12-06T00:00Z".
However, oozie instead of complaining about the data availability or directory. The error message says:
"variable [impInputData] cannot be resolved" , in fact it should have been "Dataset "impression-logs" cannot be resolved".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-630) Oozie coordinator error message
misleading
Posted by "Mohammad Kamrul Islam (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165113#comment-13165113 ]
Mohammad Kamrul Islam commented on OOZIE-630:
---------------------------------------------
This issue was already addressed in this JIRA:
http://issues.apache.org/jira/browse/OOZIE-573
This JIRA could be closed , if the resolution provided in the previous similar JIRA is sufficient.
> Oozie coordinator error message misleading
> ------------------------------------------
>
> Key: OOZIE-630
> URL: https://issues.apache.org/jira/browse/OOZIE-630
> Project: Oozie
> Issue Type: Bug
> Environment: CDH3U0, Oozie 3.0.2, Pig 8.
> Reporter: Shaik Idris Ali
> Priority: Minor
>
> My coordinator.xml has entry :
> (under datasets)
> <dataset name="impression-logs" frequency="${coord:minutes(20)}" initial-instance="2011-12-06T02:00Z" timezone="UTC">
> <uri-template>${nameNode}/user/${coord:user()}/airavat/input/HourlyImpSummary/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}/0</uri-template>
> <done-flag></done-flag>
> </dataset>
> and (under input-events)
> <data-in name="impressionInputEvent" dataset="impression-logs">
> <start-instance>${coord:current(-2)}</start-instance>
> <end-instance>${coord:current(0)}</end-instance>
> </data-in>
> and (under workflow->configuration)
> <property>
> <name>impInputData</name>
> <value>${coord:dataIn('impressionInputEvent')}</value>
> </property>
> The initial-instance="2011-12-06T11:00Z" does not exist. In fact it was a typo mistake from my side where I wanted the initial instance to be initial-instance="2011-12-06T00:00Z".
> However, oozie instead of complaining about the data availability or directory. The error message says:
> "variable [impInputData] cannot be resolved" , in fact it should have been "Dataset "impression-logs" cannot be resolved".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OOZIE-630) Oozie coordinator error message
misleading
Posted by "Harsh J (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J resolved OOZIE-630.
---------------------------
Resolution: Duplicate
> Oozie coordinator error message misleading
> ------------------------------------------
>
> Key: OOZIE-630
> URL: https://issues.apache.org/jira/browse/OOZIE-630
> Project: Oozie
> Issue Type: Bug
> Environment: CDH3U0, Oozie 3.0.2, Pig 8.
> Reporter: Shaik Idris Ali
> Priority: Minor
>
> My coordinator.xml has entry :
> (under datasets)
> <dataset name="impression-logs" frequency="${coord:minutes(20)}" initial-instance="2011-12-06T02:00Z" timezone="UTC">
> <uri-template>${nameNode}/user/${coord:user()}/airavat/input/HourlyImpSummary/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}/0</uri-template>
> <done-flag></done-flag>
> </dataset>
> and (under input-events)
> <data-in name="impressionInputEvent" dataset="impression-logs">
> <start-instance>${coord:current(-2)}</start-instance>
> <end-instance>${coord:current(0)}</end-instance>
> </data-in>
> and (under workflow->configuration)
> <property>
> <name>impInputData</name>
> <value>${coord:dataIn('impressionInputEvent')}</value>
> </property>
> The initial-instance="2011-12-06T11:00Z" does not exist. In fact it was a typo mistake from my side where I wanted the initial instance to be initial-instance="2011-12-06T00:00Z".
> However, oozie instead of complaining about the data availability or directory. The error message says:
> "variable [impInputData] cannot be resolved" , in fact it should have been "Dataset "impression-logs" cannot be resolved".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira