You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We are on airflow 3.1.3 and mostly trigger our dags via REST API and do not control logical_date (its None).
When trying to clear multiple task instances between
start_dateandend_dateusing the API endpoint/api/v2/dags/{dag_id}/clearTaskInstances, we realized that these task instances are not found and therefore not cleared.I had a look at the source code and airflow is indeed applying
start_dateandend_datefiltering on thelogical_date(which is None as described) (https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/serialization/serialized_objects.py#L3397)Is this a bug? Should the filtering work on a different attribute if logical_date is None? Is the intended use to set the logical_date explicitely?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions