From 4634b445f16ad2f6cd871c03f4435eab52077c81 Mon Sep 17 00:00:00 2001 From: zevav Date: Wed, 7 Oct 2020 13:56:02 +0200 Subject: [PATCH] typo --- blog/patch_your_idols.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/patch_your_idols.html b/blog/patch_your_idols.html index e34b95e..3309355 100644 --- a/blog/patch_your_idols.html +++ b/blog/patch_your_idols.html @@ -244,7 +244,7 @@ to happen in the first place. including their names, schedule, owner, status (paused/unpaused), recent tasks, last run, DAG runs, and links">

-The way DAGs are schedule is by supplying a CRON string to the argument +The way DAGs are scheduled is by supplying a CRON string to the argument schedule_interval. The way the Airflow GUI displays a DAG's schedule is by simply rendering the CRON string. However, not everyone "speaks CRON" on our team -- I'm one of those people, I have to Google these strings pretty much every time. What's more, I can imagine a scenario