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 2021/12/21 17:53:00 UTC

[GitHub] [airflow] eladkal commented on issue #19917: Task-level end_date stops entire DAG

eladkal commented on issue #19917:
URL: https://github.com/apache/airflow/issues/19917#issuecomment-998979129


   > For some time now -- I don't think having a "task-level" `start_date` and `end_date` makes sense !
   
   It does and it does not. It's a matter of perspective.
   I can list several use cases but for most of them there are other options to get the same functionality.
   
   One thing that we should consider is also the case of backfilling.
   For example I had a process that query a sources and does some work (task per source. after a while a new source introduced and DAG was updated with a new task with the relevant `start_date`. If for any reason i want to backfill then it didn't make any sense to schedule the task of the new source for dates prior to the creation of the source. It's a waste. This is where the `start_date` is useful on task level. Same argument could also be raised for `end_date`.


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