zhaorui2022 opened a new issue, #68582: URL: https://github.com/apache/airflow/issues/68582
### Description Similar to https://github.com/apache/airflow/issues/66839 Databricks query tags help with cost attribution and track back the origin of Databricks queries. The link issue added query tags in DatabricksSqlOperator, DatabricksCopyIntoOperator, however, there are other operators that send queries directly to Databricks and can be instrumented with query tags, that is, - DatabricksSqlSensor: https://github.com/SkastVnT/airflow/blob/ee12bab9132e0a29766e30f5cdd75cf796a53e6f/providers/databricks/src/airflow/providers/databricks/sensors/databricks_sql.py (this should also cover DatabricksPartitionSensor: https://github.com/SkastVnT/airflow/blob/ee12bab9132e0a29766e30f5cdd75cf796a53e6f/providers/databricks/src/airflow/providers/databricks/sensors/databricks_partition.py) - DatabricksSqlStatementSensor (uses a different API `DatabricksHook.post_sql_statement` to send queries): https://github.com/SkastVnT/airflow/blob/ee12bab9132e0a29766e30f5cdd75cf796a53e6f/providers/databricks/src/airflow/providers/databricks/sensors/databricks.py - DatabricksSqlStatementOperator: https://github.com/SkastVnT/airflow/blob/ee12bab9132e0a29766e30f5cdd75cf796a53e6f/providers/databricks/src/airflow/providers/databricks/operators/databricks.py#L1103 ### Use case/motivation Query tags helps to track the origin of Databricks queries, and can be used for cost attribution and etc ### Related issues https://github.com/apache/airflow/issues/66839 ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
