[GOBBLIN-1831] Use flowexecutionid in kafka monitor and jobnames

[Will-Lo]

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-1831

Description

• Here are some details about my PR, including screenshots (if applicable):
  This PR handles the scenario where concurrent jobs can run on Gobblin cluster from GaaS and handles the cancellation logic properly.

When executing jobs from GaaS to Gobblin cluster, there can be a mismatch of flowexecution ids to jobs running on Gobblin cluster. The old behavior was that the current job will be deleted regardless of the execution ID, but this could mean that a state mismatch could lead to current jobs being deleted when they should still continue to run.

To address this, we tried adding the FlowExecutionId to the jobSpec, but that meant that jobs could run concurrently on Gobblin cluster when they should have been deduped.

So instead, during cancellation, we want to check if the incoming spec has a flow execution ID. If so, then it will cancel the existing job only if the flow execution IDs match. Otherwise, it will know that the current job does not match the incoming request and should not be deleted.

This PR also uses flow execution ID if applicable as the planningjob ID and job_actualJob ID, as there should only be one of these per flow.

Tests

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

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"

[codecov-commenter]

Codecov Report

Merging #3694 (0b89d11) into master (e47aef7) will decrease coverage by 0.03%.
The diff coverage is 23.80%.

@@             Coverage Diff              @@
##             master    #3694      +/-   ##
============================================
- Coverage     46.99%   46.97%   -0.03%     
- Complexity    10788    10789       +1     
============================================
  Files          2138     2138              
  Lines         84040    84078      +38     
  Branches       9340     9344       +4     
============================================
- Hits          39497    39493       -4     
- Misses        40955    40993      +38     
- Partials       3588     3592       +4     

Impacted Files	Coverage Δ
...e/gobblin/runtime/job_monitor/KafkaJobMonitor.java	0.00% <0.00%> (ø)
...a/org/apache/gobblin/cluster/HelixJobsMapping.java	80.95% <100.00%> (+0.62%)	⬆️

... and 11 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[phet]

looks good!