feat: Add explicit support for SnowflakeSqlApiHook to Ol helper #52161
+810
−68
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
42d412d to
de1444c
Compare
|
cc @mobuchowski |
de1444c to
2477a63
Compare
|
rebasing to account for compat tests. |
mobuchowski
reviewed
Jun 30, 2025
providers/snowflake/src/airflow/providers/snowflake/utils/openlineage.py
Show resolved
Hide resolved
mobuchowski
approved these changes
Jun 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
OpenLineage is using a helper method
emit_openlineage_events_for_snowflake_queriesto emit OL events for Snowflake queries. This PR adds support for SnowflakeSqlApiHook in this helper and also adjusts some args so it's easier for users to also use this helper function in their custom code.The idea here is that users would be able to call this from within their python/custom operator and it will emit additonal OL events for each query_id with parentRunFacet pointing to the Airflow task, so the backend can still easily know about the parent/child relationship. This will allow users to easily deliver query_ids to the lineage backend even from within custom code.
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.