zev/zevaverbach.github.io
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

typo

Browse Source
This commit is contained in:
zevav
2020-10-07 13:56:02 +02:00
parent da420d649d
commit 4634b445f1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/patch_your_idols.html
View File

@@ -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">
<p>
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
<code>schedule_interval</code>. 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