This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-site.git
The following commit(s) were added to refs/heads/main by this push:
new 29621d5 Fix list on 2.2.0 blog post (#499)
29621d5 is described below
commit 29621d582a605c48e8b8238fd35fd298e599e5fd
Author: Jed Cunningham <[email protected]>
AuthorDate: Wed Oct 27 12:25:35 2021 -0600
Fix list on 2.2.0 blog post (#499)
---
landing-pages/site/content/en/blog/airflow-2.2.0/index.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/landing-pages/site/content/en/blog/airflow-2.2.0/index.md
b/landing-pages/site/content/en/blog/airflow-2.2.0/index.md
index 61632ea..1948f17 100644
--- a/landing-pages/site/content/en/blog/airflow-2.2.0/index.md
+++ b/landing-pages/site/content/en/blog/airflow-2.2.0/index.md
@@ -29,9 +29,9 @@ To provide more scheduling flexibility, determining when a
DAG should run is now
`execution_date` has long been confusing to new Airflowers, so as part of this
change a new concept has been added to Airflow to replace it named
`data_interval`, which is the period of data that a task should operate on. The
following are now available:
-`logical_date` (aka `execution_date`)
-`data_interval_start` (same value as `execution_date` for cron)
-`data_interval_end` (aka `next_execution_date`)
+- `logical_date` (aka `execution_date`)
+- `data_interval_start` (same value as `execution_date` for cron)
+- `data_interval_end` (aka `next_execution_date`)
If you write your own timetables, keep in mind they should be idempotent and
fast as they are used in the scheduler to create DagRuns.
