Description
We will encounter an issue when attempting to create a backfill with the reprocess behavior set to completed or failed, as it will trigger a unique constraint error on logical_date due to the restored uniqueness constraint.
To align with the old (2.x) behavior for existing runs that need to be reprocessed, we should ensure that when reprocessing results in a new run, the existing run is cleared. Instead of deleting the row, we update the necessary fields—similar to what was done in 2.x. This at least includes changing the state, but likely also updating start_date and possibly other relevant fields.
Use case/motivation
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Description
We will encounter an issue when attempting to create a backfill with the reprocess behavior set to
completedorfailed, as it will trigger a unique constraint error on logical_date due to the restored uniqueness constraint.To align with the old (2.x) behavior for existing runs that need to be reprocessed, we should ensure that when reprocessing results in a new run, the existing run is cleared. Instead of deleting the row, we update the necessary fields—similar to what was done in 2.x. This at least includes changing the state, but likely also updating start_date and possibly other relevant fields.
Use case/motivation
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct