Hi, almost a year ago I reported an issue to Airflow's Jira: https://issues.apache.org/jira/browse/AIRFLOW-2319
Recently, someone pointed out that I should ask here on the mailing list (I thought I did, but apparently, I did not). So here's the thing: the DagRun table has a unique constraint on (dag_id, exec_date), that was not reflected by models.py (now models/__init__.py). This got "fixed" in June 2018 - apparently this was not the only place where model declaration and schema migration scripts were out of sync. Ash now pointed out on AIRFLOW-2319, that the unique constraint is there "by design", meaning there's a reason why it's there. Can somebody please explain to me what's the reasoning behind this? For us it would be a use case to have multiple dag runs per (dag_id, exec_date). thx in advance! -- Andreas Koeltringer Mail: [email protected]
