Re: [DISCUSS] Java SDK and the Language Coordinator Layer [was: LAZY CONSENSUS]

[Tzu-ping Chung via dev]

> On 13 May 2026, at 20:42, Jarek Potiuk <ja...@potiuk.com> wrote:
> 
> Not really. I proposed an internal package that can be changed **any time**. 
> Users aren't supposed to use those items. We can clearly mark them with "_" 
> and also describe them thoroughly in the public API documentation. And no. 
> Initilaly providers were **not** in arflow at all - you started from step 2. 
> Step 1 is that they were added at some point in time long before my time. 
> Hooks and operators as "API" were creaed quite early in the concept of 
> Airflow - and the first implementations were added then. Then, after common 
> patterns emerged, those hooks and operators were grouped into providers (they 
> were not initially) and only moved out after quite some time. As I see it - 
> you even admit yourself that things will look differently for different 
> languages, and maybe even we will not need bridges for some of them at all. 
> So why should we introduce new concept if we know currrently that it applies 
> only to "JDK"? I fail to see why we should proceed if we already know the 
> patterns are unlikely to be reusable in their current form.

How do you make it changeable any time? User needs to be able to specify what 
coordinator to use in the config, and you can’t break that later.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org