[GitHub] [airflow] eladkal commented on issue #17734: Backfilling ignores task-level start_date and end_date

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

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


   It make sense that backfill should respect the task definition for tasks `start_date` and `end_date`.
   If we have a dag as:
   ```
   with DAG(
       'my_dag',
       default_args=default_args,
       schedule_interval='@daily',
       start_date=datetime(2019, 1, 1),
   ) as dag:
       t1 = BashOperator(
           task_id='print_date',
           bash_command='date',
       )
         t2 = BashOperator(
           task_id='print_date2',
           bash_command='date',
           start_date=datetime(2021, 1, 1)
       )
   ```
   
   and you are running `airflow dags backfill my_dag --start-date 2019-01-01 --end-date 2019-06-01`
   I wouldn't expect `print_date2` to be a part of this backfill at all. To my perspective the backfill `start-date` & `stop-date` specify the range of runs that needs to be created - in these runs it doesn't make sense to consider tasks that are not part of this window.
   
   If someone has a different take on that I would love to hear the reasons
   


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