You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@airflow.apache.org by Jens Scheffler <js...@apache.org> on 2026/03/30 21:30:40 UTC

[RESULT][VOTE] Improve problems of additional latency for tasks returning from Triggerer to Worker

Hi Airflow Devs,

thanks for the voting and feedback as of thread in devlist 
https://lists.apache.org/thread/rxgfgj8j235hrrns13wcjptcnbxokfrd . 
Aggregated results from the voting are:

  * OPTION A) Integrate feature to directly queue tasks from Triggerer
    as of PR https://github.com/apache/airflow/pull/63489 in Airflow 3.2.0
      o +0.8 / -0.5 / -1 / -1 (binding) | -1 (non-binding)
  * OPTION B) Extend Triggerer to support XCom, change KPO to end from
    Triggerer as of PR
    https://github.com/apache/airflow/pull/64068 (Core) with Target
    Airflow 3.2.0 and https://github.com/apache/airflow/pull/64069 (KPO
    Adjustment)
      o +1 / 0 / -0.1 / -0.1 (binding) | 0 (non-binding)
  * OPTION C) Do not immediately change this for Airflow 3.2.0, further
    discuss alternatives, e.g. raise an AIP
      o +0 / +1 / +1 / +1 (binding) | +1 (non-binding)

Which means that clearly Option C) is preferred. Will attempt to drive a 
AIP during the next time to have all details and options nailed down for 
an implementation plan, hope to have it in Airflow 3.3.0 then

Jens

Re: [RESULT][VOTE] Improve problems of additional latency for tasks returning from Triggerer to Worker

Posted by Vikram Koka via dev <de...@airflow.apache.org>.

Thanks Jens, for taking the initiative and driving this through a
transparent process.
Happy to help you in any way on this (hopefully small) AIP.

Vikram


On Mon, Mar 30, 2026 at 2:31 PM Jens Scheffler <js...@apache.org> wrote:

> Hi Airflow Devs,
>
> thanks for the voting and feedback as of thread in devlist
> https://lists.apache.org/thread/rxgfgj8j235hrrns13wcjptcnbxokfrd .
> Aggregated results from the voting are:
>
>   * OPTION A) Integrate feature to directly queue tasks from Triggerer
>     as of PR https://github.com/apache/airflow/pull/63489 in Airflow 3.2.0
>       o +0.8 / -0.5 / -1 / -1 (binding) | -1 (non-binding)
>   * OPTION B) Extend Triggerer to support XCom, change KPO to end from
>     Triggerer as of PR
>     https://github.com/apache/airflow/pull/64068 (Core) with Target
>     Airflow 3.2.0 and https://github.com/apache/airflow/pull/64069 (KPO
>     Adjustment)
>       o +1 / 0 / -0.1 / -0.1 (binding) | 0 (non-binding)
>   * OPTION C) Do not immediately change this for Airflow 3.2.0, further
>     discuss alternatives, e.g. raise an AIP
>       o +0 / +1 / +1 / +1 (binding) | +1 (non-binding)
>
> Which means that clearly Option C) is preferred. Will attempt to drive a
> AIP during the next time to have all details and options nailed down for
> an implementation plan, hope to have it in Airflow 3.3.0 then
>
> Jens
>