Lee-W commented on code in PR #47074:
URL: https://github.com/apache/airflow/pull/47074#discussion_r1970992362
##########
airflow/config_templates/config.yml:
##########
@@ -2661,7 +2661,36 @@ scheduler:
type: boolean
example: ~
default: "True"
- see_also: ":ref:`Differences between the two cron timetables`"
+ see_also: ':ref:`Differences between "trigger" and "data interval"
timetables`'
+ create_delta_data_intervals:
+ description: |
+ Whether to create DAG runs that span an interval or one single point
in time when a timedelta or
+ relativedelta is provided to ``schedule`` argument of a DAG.
+
+ * ``True``: **DeltaDataIntervalTimetable** is used, which is suitable
for DAGs with well-defined data
+ interval. You get contiguous intervals from the end of the previous
interval up to the scheduled
+ datetime.
+ * ``False``: **DeltaTriggerTimetable** is used, which is suitable for
DAGs that simply want to say
+ e.g. "run this every day" and do not care about the data interval.
+
+ Notably, for **DeltaTriggerTimetable**, the logical date is the same
as the time the DAG Run will
+ try to schedule, while for **DeltaDataIntervalTimetable**, the logical
date is the beginning of
+ the data interval, but the DAG Run will try to schedule at the end of
the data interval.
+ version_added: 2.11.0
+ type: boolean
+ example: ~
+ default: "True"
+ see_also: ':ref:`Differences between "trigger" and "data interval"
timetables`'
+ enable_tracemalloc:
+ description: |
+ Whether to enable memory allocation tracing in the scheduler. If
enabled, Airflow will start
+ tracing memory allocation and log the top 10 memory usages at the
error level upon receiving the
+ signal SIGUSR1.
+ This is an expensive operation and generally should not be used except
for debugging purposes.
+ version_added: 3.0.0
Review Comment:
Should it be 2.11.0 instead?
--
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]
