[OOZIE-573] error message about misconfig in starting time of coordinator and initial-instance of dataset

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: pre-Apache
• Assignee: Unassigned
• Reporter: Parameswaran Raman
• Created: 05/Oct/11 20:50
• Updated: 13/May/12 00:18
• Resolved: 17/Oct/11 23:26

Description

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)"