[
https://issues.apache.org/jira/browse/OOZIE-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437366#comment-15437366
]
Purshotam Shah commented on OOZIE-2647:
---------------------------------------
It will happen for -2 or -10, they fall out of the initial instance.
For -2
If your initial-instance is {{startTime}} and job start time is also
{{startTime}}. So for 1st and 2nd action, current(-2) is nothing because they
all out of initial-instance.
> input-events is always ignored for the first action (WF) of the coordinator
> if the instance is set to ${coord:current(-1)}
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-2647
> URL: https://issues.apache.org/jira/browse/OOZIE-2647
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 4.1.0
> Environment: Oozie client build version: 4.1.0-cdh5.8.0
> Reporter: Burak Gursoy
> Attachments: 01-coordinator.xml, 01-job-state.txt,
> 01-schedule-minus-one.txt, 01-workflow.xml, 02-coordinator.xml,
> 02-job-state.txt, 02-schedule-zero.txt, 02-workflow.xml, job.properties
>
>
> Hi,
> We've noticed that if you have a definition like this in the coordinator.xml,
> then the first action is always released and the existence of the data
> dependency is never checked/verified. This only seems to happen with the
> value "-1" and nothing else ("0", any other positive or negative value seems
> to be fine).
> I currently don't have access to a more recent release, but I also couldn't
> locate a bug related to this in here.
> {code}
> <input-events>
> <data-in name="input-my-dataset" dataset="my-dataset">
> <instance>${coord:current(-1)}</instance>
> </data-in>
> </input-events>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
