[GitHub] [airflow] potiuk commented on issue #8494: TriggerDagOperator sometimes causes database to trigger UniqueViolation constraint

[GitBox <gi...@apache.org>]

potiuk commented on issue #8494:
URL: https://github.com/apache/airflow/issues/8494#issuecomment-884118023


   There has been a bit overhaul of DAG triggering in Airflow 2 and there is a different primary index on DagRun and we are also preparing for making "out-of-band" triggering a DagRun which is not connected with particular interval. So I think this issue is either gone entirely already in Airflow 2, or when we release "AIP-39 - Richer scheduler interval" I think it will be the final step to consider that non-issue. So I agree with @uranusjr that this one should be closed.
   
   BTW. If you have not yet migrated to 1.10, do it now. It wont receive any fixes any more (including critical security fixes). In fact there are already known security problems which have not been patched in 1.10 - you can get more insight by watching our talk from the Airflow Summit: "Keep your Airflow Secure" https://www.crowdcast.io/e/airflowsummit2021/3


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org