tatiana opened a new issue, #40587:
URL: https://github.com/apache/airflow/issues/40587

   ### Apache Airflow Provider(s)
   
   databricks
   
   ### Versions of Apache Airflow Providers
   
   6.7.0
   
   ### Apache Airflow version
   
   2.9
   
   ### Operating System
   
   all
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   N/A
   
   ### What happened
   
   N/A
   
   ### What you think should happen instead
   
   To expose repair and repair all tasks, the Databricks provider 6.7.0 relies 
on the soon-to-be-deprecated Airflow 2.x plugins. This was introduced in 
#40153. This is one of the most used features of the original 
https://github.com/astronomer/astro-provider-databricks, and we're completing 
the migration with this PR. I've interacted with at least five Astronomer 
customers who use this feature, and the project has received over 115k monthly 
downloads on PyPI.
   
   To use plugins is suboptimal, but as of Airflow 2.9,  the core Airflow 
doesn't offer a better way to implement this feature, as discussed in the 
thread:
   https://github.com/apache/airflow/pull/40153#discussion_r1663852033
   
   As part of Airflow 3.x, we want to find a better way to allow providers to 
implement this feature type. @potiuk is going to help us log this into the 3 
roadmap, and Astronomer commits to migrating the repair and job links to the 
Airflow 3.x strategy once it is available.
   
   ### How to reproduce
   
   N/A
   
   ### Anything else
   
   N/A
   
   ### Are you willing to submit PR?
   
   - [X] 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]

Reply via email to