apache/airflow

Improve Databricks operators with query tags

Open

#66839 opened on May 13, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Python (44,809 stars) (16,781 forks)batch import
good first issuekind:featureprovider:databricks

Description

Description

Databricks supports query tags which allows us to track where the source of a query is on Databricks UI. Reference: https://docs.databricks.com/aws/en/sql/user/queries/query-tags

Currently when a query is sent to Databricks, on Databricks UI, the only info we can see is the query is from Airflow, but there is no other metadata like airflow dag id, task id, run id and etc.

Use case/motivation

With query tags instrumented, it will be easy for organizations to track and do Databricks cost contribution across different Airflow DAGs.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
python
Domain
backenddata
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of Apache Airflow operatorsFamiliarity with Databricks SQLPython programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the existing Databricks operators in the Airflow providers package (e.g., airflow/providers/databricks/operators/). Understand the query tag documentation from Databricks to see how tags are passed. Consider adding a parameter to the operators for query tags and ensure they are attached to each query execution. Check for any existing PRs or discussions on the issue for implementation details.