GolikovAndrey commented on issue #15150:
URL: https://github.com/apache/airflow/issues/15150#issuecomment-1785136347

   > > Seems strange to have that unique constraint. If two DAG runs have 
different run_ids, why not let them run at the same time?
   > 
   > Because historically execution date was the key not run_id and the whole 
datamodel was based on execution_date being part of foreign key in multiple 
tables. This has since been removed and in Airflow 2.2 the primary key is 
run_id and execution_date is just a field. See the changelog 
https://airflow.apache.org/docs/apache-airflow/2.2.4/changelog.html#airflow-2-2-0-2021-10-11
   
   Now we have Airflow v. 2.6.3, but I still see field execution_date in 
constrained fields (uniqueness constraint).
   
![image](https://github.com/apache/airflow/assets/61521604/22d25cfc-7ae7-4c1d-9982-4e6681a8712d)


-- 
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]

Reply via email to