yuqian90 commented on a change in pull request #7038: [AIRFLOW-4495] allow
externally triggered dags to run for future exec dates
URL: https://github.com/apache/airflow/pull/7038#discussion_r363138205
##########
File path: airflow/models/dag.py
##########
@@ -778,16 +778,26 @@ def set_dependency(self, upstream_task_id,
downstream_task_id):
def get_task_instances(
self, start_date=None, end_date=None, state=None, session=None):
if not start_date:
+ # TODO why 30?
start_date = (timezone.utcnow() - timedelta(30)).date()
start_date = timezone.make_aware(
datetime.combine(start_date, datetime.min.time()))
- end_date = end_date or timezone.utcnow()
- tis = session.query(TaskInstance).filter(
- TaskInstance.dag_id == self.dag_id,
- TaskInstance.execution_date >= start_date,
- TaskInstance.execution_date <= end_date,
- TaskInstance.task_id.in_([t.task_id for t in self.tasks]),
- )
+
Review comment:
This change to `get_task_instances()` seems to be newly included from the
previously closed PR? This is going to change the TI returned to include those
considered in the "future". Why is this change necessary?
If it is indeed needed, you should probably consider doing the same as what
you did in `scheduler_job.py`, i.e. only include "future" tasks if
`RUN_FUTURE_EXEC_DATES` is True **and** `dag.schedule_interval` is None
----------------------------------------------------------------
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:
[email protected]
With regards,
Apache Git Services
