gshand-beta commented on issue #15150: URL: https://github.com/apache/airflow/issues/15150#issuecomment-1118966712
> The DagRun table has the following constraints: > > https://github.com/apache/airflow/blob/83d702c345f8f4ce16d32268f4f83ee508fea676/airflow/models/dagrun.py#L96-L97 > > which is why you can't create / trigger a DagRun that violates it i.e. you can't trigger a DAG with same `execution_date` or with same `run_id`. Seems strange to have that unique constraint. If two DAG runs have different run_ids, why not let them run at the same time? Can anyone provide context as to why that constraint is necessary? If you're invoking DAG runs from multiple processes running concurrently, it's pretty easy to run into this issue. I'd classify this as a bug, as expected behavior is that Airflow should be able to tolerate concurrent invocations. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
