uranusjr commented on PR #68749: URL: https://github.com/apache/airflow/pull/68749#issuecomment-4774953008
> re-running for a 3-month-old event would just read today's data anyway This entirely depends on how the task actually reads data, doesn’t it? If it just reads the current data, the same argument can be made against scheduled catchups too. For catchup to work, you need to implement the task in a way that makes catchup possible in the first place. With scheduled dags, this means it should use the data interval or logical date. With assets, it should use the asset event date, which would be in the past. I don’t think this argument holds. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
