Hey Niko, Thanks for kicking off this discussion!
I’m fully on board with removing support for hardcoded hybrid executors in favor of multi-executor support for 3.0—it’s a great step forward in simplifying execution models. Adding deprecation warnings in 2.11 also makes sense to give users a smooth transition period. Regarding marking multi-executor support stable in 2.11: The only thing I’d be mindful of is ensuring we get enough real-world testing across different multi-executor combinations before marking it fully stable. We haven’t seen a ton of feedback on that front yet, and I’d rather avoid unexpected surprises post-release. Also, since we’re focused on wrapping up 3.0, I’d prefer to keep changes in 2.11 minimal where possible. Deprecation warnings are a great addition, but I’d want to avoid creating any expectations that we’ll be patching 2.11 specifically for this feature now that it’s considered stable. Curious to hear what others think! Cheers, Constance On Thu, Feb 13, 2025 at 8:16 PM Oliveira, Niko <oniko...@amazon.com.invalid> wrote: > Hello folks! > > Multiple Executor Configuration (aka hybrid executors, AIP-61) has been > out a while now and we haven't had many issues with it. I'm proposing we > mark it as stable. > > Relatedly I would also like to discuss removing support for the older > hardcoded hybrid executors (e.g. CeleryKubernetesExecutor, etc) in Airflow > 3. We still have many lines of code in core Airflow that are coupled > directly to these executors since they need special handling. They also > don't track changes to the base executor very well and so they tend to > break every time that interface changes [2]. I figure Airflow 3.0 might be > the best opportunity we'll have in a while to remove these executors. > > We of course don't have to remove them from the provider packages they > live in, so new versions of providers will still be compatible with pre 3.0 > Airflow to use those executors. > > I propose that we mark Multiple Executor Configuration stable in 2.11 and > clearly mark the old hardcoded hybrid executors as deprecated also in 2.11. > This gives time for folks to migrate if they'd like. Then in 3.0 remove all > our special handling and testing from core Airflow relating to these > hardcoded hybrid executors. > > What do y'all think? > > Cheers, > Niko > > [1] - https://github.com/apache/airflow/pull/46742 > [2] - https://github.com/apache/airflow/pull/41602 >
