[
https://issues.apache.org/jira/browse/OOZIE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122254#comment-13122254
]
[email protected] commented on OOZIE-573:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2225/#review2413
-----------------------------------------------------------
Committed
- Mohammad
On 2011-10-05 21:07:07, params wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/2225/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-10-05 21:07:07)
bq.
bq.
bq. Review request for oozie, Mohammad Islam and Angelo K. Huang.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. OOZIE-573: error message about misconfig in starting time of coordinator
and initial-instance of dataset
bq.
bq. Summary:
bq. https://issues.apache.org/jira/browse/OOZIE-573
bq.
bq.
bq. This addresses bug OOZIE-573.
bq. https://issues.apache.org/jira/browse/OOZIE-573
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. trunk/core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java
1179437
bq. trunk/release-log.txt 1179437
bq.
bq. Diff: https://reviews.apache.org/r/2225/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Tested against current test cases.
bq.
bq.
bq. Thanks,
bq.
bq. params
bq.
bq.
> 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
