You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Parameswaran Raman (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/18 01:27:10 UTC
[jira] [Resolved] (OOZIE-573) error message about misconfig in
starting time of coordinator and initial-instance of dataset
[ https://issues.apache.org/jira/browse/OOZIE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Parameswaran Raman resolved OOZIE-573.
--------------------------------------
Resolution: Fixed
Changes have been committed. Marking as fixed.
> error message about misconfig in starting time of coordinator and initial-instance of dataset
> ---------------------------------------------------------------------------------------------
>
> Key: OOZIE-573
> URL: https://issues.apache.org/jira/browse/OOZIE-573
> Project: Oozie
> Issue Type: Bug
> Reporter: Parameswaran Raman
>
> When initial-instance of dataset points to some timestamp later than starting time of coordinator job (by mistake) , coordinator cannot resolve coord:current(0) of the dataset right after it starts. Therefore, it returns an empty string. This behavior itself is expected, but adding a log (warning) message could be more helpful for debugging purposes.
> in this particular case, user facing this issue tried to insert coord:current(0) to variable
> ====
> <output-events>
> <data-out name="path_mvp_dataout" dataset="path_mvp_dataset">
> <instance>${coord:current(0)}</instance>
> </data-out>
> </output-events>
> =====
> and found following error message
> "variable [path_mvp_output] cannot be resolved use coord:current(0)"
--
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