Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-2647

input-events is always ignored for the first action (WF) of the coordinator if the instance is set to ${coord:current(-1)}

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 4.1.0
    • None
    • coordinator
    • None
    • Oozie client build version: 4.1.0-cdh5.8.0

    Description

      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.

        <input-events>
          <data-in name="input-my-dataset" dataset="my-dataset">
            <instance>${coord:current(-1)}</instance>
          </data-in>
        </input-events>
      

      Attachments

        1. 01-coordinator.xml
          1.0 kB
          Burak Gursoy
        2. 01-job-state.txt
          3 kB
          Burak Gursoy
        3. 01-schedule-minus-one.txt
          0.7 kB
          Burak Gursoy
        4. 01-workflow.xml
          1 kB
          Burak Gursoy
        5. 02-coordinator.xml
          1.0 kB
          Burak Gursoy
        6. 02-job-state.txt
          3 kB
          Burak Gursoy
        7. 02-schedule-zero.txt
          0.7 kB
          Burak Gursoy
        8. 02-workflow.xml
          1 kB
          Burak Gursoy
        9. job.properties
          0.0 kB
          Burak Gursoy

        Activity

          People

            Unassigned Unassigned
            burak Burak Gursoy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: