apache/airflow

Improve Databricks operators with query tags

已關閉

#66,839 建立於 2026年5月13日

在 GitHub 查看貢獻者指南
 (5 則留言) (0 個反應) (0 位負責人)Python (16,781 個分叉)batch import
good first issuekind:featureprovider:databricks

倉庫指標

星標
 (44,809 顆星)
PR 合併指標
 (平均合併 7天 18小時) (30 天內合併 834 個 PR)

描述

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

貢獻者指南

研究方向
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.
技術棧
python
領域
backenddata
議題類型
功能
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 天
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
活躍
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
清晰
前置要求
Basic understanding of Apache Airflow operatorsFamiliarity with Databricks SQLPython programming
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50