feat: Add supported hooks to OpenLineage docs #41958
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.
As Hook Level Lineage (AIP-62) is now live, we should update OpenLineage docs by adding supported hooks.
Also, here is a preview of the change:
Before:
After:
Side notes:
For now, we only check for classes for full calls like
get_hook_lineage_collector().add_input_dataset(...)
orget_hook_lineage_collector().add_output_dataset(...)
. Any other call will not be detected. Statically detecting these calls is challenging, so for now we should probably leave it like this, on a best effort basis with an important notice at the top.Also, I don't think we can cross reference that with OL translators provided for schema in all providers and detect which hook has OL translator provided. We can assume that when adding hook level lineage, one will try to add ol translator as well. I'll try to work on some most popular hooks soon.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.