You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/02/04 01:23:26 UTC

[GitHub] [airflow] pbotros commented on issue #7038: [AIRFLOW-4495] Allow externally triggered dags to run for future exec dates

pbotros commented on issue #7038: [AIRFLOW-4495] Allow externally triggered dags to run for future exec dates
URL: https://github.com/apache/airflow/pull/7038#issuecomment-581698426
 
 
   Sorry for the comment spam on a merged PR, but a quick follow-up to @kaxil's comment above:
   
   > DAG is scheduled to run every day at 5 PM
   > 1. Dag is triggered for a future date (ex: 10 Jan 2020 17:00:00) and succeeds
   > 2. 10 Jan arrives, Scheduler tries to run it but fails because it violates unique key constraint
   
   What if this is the use case we _want_ to support? i.e.: DAG is scheduled to run every day at 5 PM, and let's say I did some upstream data changes. I'm impatient and want to run the DAG at 4pm for one particular day instead of 5pm. Ideally:
   
   - Trigger dag with a future date (ex: 3 Feb 2020 17:00:00) at 4pm via airflow CLI; succeeds
   - 5pm arrives, and the scheduler handles the unique key constraint gracefully and does not run the DAG
   
   @kaxil @yuqian90 et al, thoughts on the above? Said another way, the proposal is to extend `allow_trigger_in_future` to all DAGs, including ones with a `schedule_interval`, by handling the unique constraint gracefully.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services