Fix #2735 - Simplify Airflow properties extraction #2749
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes :
This PR fixes #2735
We were encountering a known issue (apache/airflow#20875) when trying to extract DAG and Task properties using airflow's serialiser. That issue was fixed after 2.2.3 release (so we would still need to wait for 2.2.4).
In this PR we are ditching the serialiser completely and instead, we use Airflow models for DAG, DagRun and TaskInstance to extract all necessary data. As all this information is available in the
context
of the lineage and callbacks, we can just pick this info up from the actual Airflow objects.This lets us play safely on 2.2.3. However, for Airflow 1.10.15, further work is required. More info #2748
Thanks!
Type of change :
Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.
Checklist:
Reviewers