Job parent hierarchy

[collado-mike]

Problem

Database migration as described in #1928 . This implements the database migration necessary to create the new columns (job_uuid and parent_run_id in runs and parent_job_uuid in jobs.

Solution

This PR addresses only the migration. After merging this, a deployment will have the new columns and values will be present, but aren't being actively written by the code and aren't being read. The migration is intended to be fully backward compatible, so if a deployment needs to be rolled back, the original data/behavior is preserved.

I added a jobs_view that calculates the fully qualified name rather than storing the FQN directly. With this implementation, a parent job can be renamed and child jobs can automatically be renamed (we'll need a separate issue to automatically redirect, as that's not currently handled in this impl). We also use the simple name of the job to display in the UI (currently relying on parsing the dot characters in the name). If we store the FQN directly, we'll need to parse the FQN to derive the simple name for display. On the other hand, constructing the FQN after storing the simple name is easy and cheap. While the view adds some complexity, I think it gives us direct access to the information we want without forcing us to use heuristics to figure it out.

Note: All database schema changes require discussion. Please link the issue for context.

Checklist

• You've signed-off your work
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• You've updated any relevant documentation (if relevant)
• You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
• You've versioned your .sql database schema migration according to Flyway's naming convention (if relevant)

[wslulciuc]

Thanks for entertaining my thoughts and feedback @collado-mike. Left some minor comment, and suggestion to rename a few columns, but otherwise great work! 💯 🥇

[codecov]

Codecov Report

Merging #1935 (a8ccb62) into main (ac7a455) will decrease coverage by 0.03%.
The diff coverage is 78.94%.

@@             Coverage Diff              @@
##               main    #1935      +/-   ##
============================================
- Coverage     78.23%   78.20%   -0.04%     
  Complexity      955      955              
============================================
  Files           194      194              
  Lines          5293     5303      +10     
  Branches        420      420              
============================================
+ Hits           4141     4147       +6     
- Misses          706      713       +7     
+ Partials        446      443       -3     

Impacted Files	Coverage Δ
api/src/main/java/marquez/db/JobDao.java	100.00% <ø> (ø)
api/src/main/java/marquez/db/JobVersionDao.java	89.39% <ø> (ø)
api/src/main/java/marquez/api/JobResource.java	92.30% <57.14%> (-5.52%)	⬇️
api/src/main/java/marquez/service/RunService.java	87.67% <66.66%> (ø)
api/src/main/java/marquez/MarquezContext.java	84.93% <100.00%> (ø)
api/src/main/java/marquez/db/OpenLineageDao.java	96.29% <100.00%> (+0.02%)	⬆️
api/src/main/java/marquez/db/RunDao.java	92.50% <100.00%> (-0.10%)	⬇️
.../src/main/java/marquez/service/LineageService.java	84.46% <100.00%> (+0.46%)	⬆️
...va/marquez/graphql/mapper/LineageResultMapper.java	63.63% <0.00%> (-3.04%)	⬇️

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[wslulciuc]

Thanks for addressing my comments! Left one minor suggestion on naming, otherwise 👍

[wslulciuc]

_Minor: I would also update the migration script to reflect the name of the column added:

V43__alter_jobs_add_job_parent_uuid.sql