potiuk commented on PR #35965: URL: https://github.com/apache/airflow/pull/35965#issuecomment-1882890410
> I know it is late to comment this but we're using DaskExecutor here in production and it quite good, config easier than celery as it not require broker backend like redis. And you can still use it, it will just not be maintained any more by the community. You can keep latest `apache-airflow-provider-daskexecutor` provider installed in future versions of Airflow and keep using it. No problem with that - it will just not be maintained and tested in the main version of Airflow. We will keep on releasing and fixing security issues (if found) but we will not add new few features and will not keep up with latest dask libraries. This is possible thanks to implementing "AIP-51 Remove Executor Coupling" https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-51+Removing+Executor+Coupling+from+Core+Airflow - where we designed and implemented public executor API that is intended to be backwards-compatible in the future. Thanks to that, latest released `daskexecutor` provider https://pypi.org/project/apache-airflow-providers-daskexecutor/ **should** work with future Airflow versions. Of course if someone would like to keep on maintaining it, adding new libraries, possibly adding new features, and release a new executor based on the daskexecutor code that we have here tagged - they are absolutely free to do so. Our code is released with [Apache Software Licence ](https://www.apache.org/licenses/LICENSE-2.0) which allows anyone to do anything with the code and make a fork and release updated provider version on their own. We actually encourage that and will be happy to merge a change with link to such fork to our https://airflow.apache.org/ecosystem/ page where we have multiple providers, plugins, extensions, tools etc. We know also a number of people and teams are working on their own executors (again, following the clean API implemented and published with AIP-51), so having somoene developing and releasing Dask Executor, that someone would like to commit to maintain and release in the future would be one of those. -- 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]
