[GOBBLIN-2134] update job status to SKIPPED for all the dependent jobs of a cancelled job

[arjun4084346]

Dear Gobblin maintainers,

Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!

JIRA

• My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
  • https://issues.apache.org/jira/browse/GOBBLIN-2134

Description

• Here are some details about my PR, including screenshots (if applicable):
  created SKIPPED execution status
  used it for the jobs that cannot be run because it's parent job is cancelled

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:
  updated tests in KillDagProcTest

Commits

• My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

[arjun4084346]

the first job was launched, but we are cancelling the 3rd job, so the cancelParams will not have "SPEC_PRODUCER_SERIALIZED_FUTURE". this is realized when i fixed the test mock behavior above

[Will-Lo]

Need to test this thoroughly with unit tests, I believe this can cause the JobStatusMonitor to have some issues since it doesn't have SKIPPED in the JobStatusMonitor ordered execution statuses?

[arjun4084346]

Need to test this thoroughly with unit tests, I believe this can cause the JobStatusMonitor to have some issues since it doesn't have SKIPPED in the JobStatusMonitor ordered execution statuses?

This change is not emitting SKIPPED event, so JobStatusMonitor will never get any such event. It is just updating the status in DagNode. But yes, let me update the code to actually emit the event so get job status call show the job status as SKIPPED; and incorporate it in ORDERED_EXECUTION_STATUS