2024 6:13:31 PM
>> To: dev@airflow.apache.org
>> Subject: [EXT] [DISCUSS] allow_trigger_in_future setting: keep or chop?
>>
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you can confirm the sender and know
>>
__
> From: Daniel Standish
> Sent: Thursday, August 15, 2024 6:13:31 PM
> To: dev@airflow.apache.org
> Subject: [EXT] [DISCUSS] allow_trigger_in_future setting: keep or chop?
>
> CAUTION: This email originated from outside of the organization. Do not
> click li
PM
To: dev@airflow.apache.org
Subject: [EXT] [DISCUSS] allow_trigger_in_future setting: keep or chop?
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
AVERTISSEMENT: Ce courrier électroniqu
This setting, which affects scheduler behavior in a few places, seems like
the type of thing that should not be configurable.
I would propose we either always allow or always don't allow. Does anyone
remember why we made it configurable?
I don't have a strong feeling re allow or don't, but I gue
