SamWheating commented on code in PR #29909:
URL: https://github.com/apache/airflow/pull/29909#discussion_r1133149457
##########
airflow/timetables/simple.py:
##########
@@ -108,6 +109,37 @@ def next_dagrun_info(
return DagRunInfo.exact(run_after)
+class ContinuousTimetable(_TrivialTimetable):
+ """Timetable that schedules continually, while still respecting start_date
and end_date
+
+ This corresponds to ``schedule="@continuous"``.
+ """
+
+ description: str = "As frequently as possible while still obeying
max_active_runs"
Review Comment:
> Also this one: Can we provide data interval as (None, current_start_date)
for the first run and (previous_start_date, current_start_date) for the next
dag runs?
Looking into this, I think that the data interval must be composed of valid
Datetimes (not None) and I think it would be most accurate to use
`(dag.start_date, utcnow())` for the first interval and `(previous_end_date,
utcnow())` for successive runs.
Does this sound agreeable, @hussein-awala ?
--
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]
