Move lineage mechanism to sdk #48379
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
uranusjr
commented
Mar 26, 2025
Comment on lines
-74
to
-77
| .. note:: Behind the scenes Airflow prepares the lineage metadata as part of the ``pre_execute`` method of a task. When the task | ||
| has finished execution ``post_execute`` is called and lineage metadata is pushed into XCOM. Thus if you are creating | ||
| your own operators that override this method make sure to decorate your method with ``prepare_lineage`` and ``apply_lineage`` | ||
| respectively. |
Member
Author
There was a problem hiding this comment.
The hooks are now unconditionally called in the sdk, so the decorators are no longer needed.
uranusjr
force-pushed
the
lineage-in-sdk
branch
from
c2de4b2 to
9f9eeda
Compare
uranusjr
force-pushed
the
lineage-in-sdk
branch
from
9f9eeda to
b8190e4
Compare
7 tasks
uranusjr
force-pushed
the
lineage-in-sdk
branch
2 times, most recently
from
2653b18 to
8d13d86
Compare
The LineageBackend base class is moved to sdk.definitions. Runtime mechanism in airflow.lineage now lives in sdk.execution_time and also called in the task runner. Lineage hook and collectors are left in Core. You can make a case they can be in the sdk, but it's not necessarily so I'm keeping the work simple for now. I left a compatibility layer in Core, but will submit a PR later to remove it and rewrite related usages.
uranusjr
force-pushed
the
lineage-in-sdk
branch
from
8d13d86 to
8fc45a0
Compare
Member
Author
|
Going to remove |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The LineageBackend base class is moved to sdk.definitions. Runtime mechanism in airflow.lineage now lives in sdk.execution_time and also called in the task runner.
Lineage hook and collectors are left in Core. You can make a case they can be in the sdk, but it's not necessarily so I'm keeping the work simple for now.
I left a compatibility layer in Core, but will submit a PR later to remove it and rewrite related usages.
A part of #45424. Close #47771.