feat: Add OpenLineage methods to DatabricksHook#62179
Merged
mobuchowski merged 1 commit intoapache:mainfrom Feb 23, 2026
Merged
feat: Add OpenLineage methods to DatabricksHook#62179mobuchowski merged 1 commit intoapache:mainfrom
mobuchowski merged 1 commit intoapache:mainfrom
Conversation
Contributor
Author
|
@mobuchowski ptal |
7e47624 to
6df0216
Compare
6df0216 to
e575a9c
Compare
mobuchowski
approved these changes
Feb 23, 2026
Contributor
mobuchowski
left a comment
There was a problem hiding this comment.
we need to standarize databricks lineage too in OpenLineage's dataset naming
xvega
pushed a commit
to xvega/airflow
that referenced
this pull request
Feb 24, 2026
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.
Adding OL methods to DatabricksHook, so that we can compute databricks OL namespace when gathering hook level lineage #62171 . Ol namespace is required when creating ExternalQueryRunFacet, that contains query_id of executed query.
So far we've only added those methods to DbApiHook based classes, but we can also add them to other hooks - they will not be used in BaseSQLOperator children anyway, as there is a check for DbApiHook inheritance there. So we can safely add OL db methods to different hooks, so that our sql parser can take advantage of it.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.