feat: Improve Hook Level Lineage for BigQueryHook#62231
Open
kacpermuda wants to merge 1 commit intoapache:mainfrom
Open
feat: Improve Hook Level Lineage for BigQueryHook#62231kacpermuda wants to merge 1 commit intoapache:mainfrom
kacpermuda wants to merge 1 commit intoapache:mainfrom
Conversation
0ee47cd to
abb61a1
Compare
shahar1
reviewed
Feb 21, 2026
Contributor
shahar1
left a comment
There was a problem hiding this comment.
Compatibility tests with 2.11 failed - please check it out
abb61a1 to
9503054
Compare
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
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.
Followup to #61535, where I left a TODO for BigqueryHook. This PR extends Hook Level Lineage support for BigQueryHook.insert_job to non-query job types. Also, by adding OL methods to the hook, we can now create an OL namespace for SqlParser, which means when reading Hook Level Lineage in OL provider, we can attach BQ job_id as a facet.
Was generative AI tooling used to co-author this PR?
Generated-by: Cursor following the guidelines
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.