Body

Once we've restored uniqueness on logical date, backfill logic can be made a bit simpler.

We should go through, and in places where we guard against the possibility of multiple runs for a given logical date, we should simplify the logic.

Additionally, in places where we do locking to avoid the creation of multiple concurrent runs for a given logical date, we should just rely on the fact that there is a unique constraint to protect us.

We also need to restore the old (2.x) behavior re existing runs that need to be reprocessed. When the reprocess behavior would result in a new run, we clear the existing run. We don't delete the row but update the fields that need to be updated -- whatever was done in 2.x. At least this means changing the state, but probably also start_date and maybe other fields as well.

(reference: https://cwiki.apache.org/confluence/display/AIRFLOW/Option+2+clarification+doc+WIP)

Committer

• I acknowledge that I am a maintainer/committer of the Apache Airflow project.