You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2020/12/17 18:48:52 UTC
[airflow-site] branch master updated: Minor typo (#357)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airflow-site.git
The following commit(s) were added to refs/heads/master by this push:
new 4b976bb Minor typo (#357)
4b976bb is described below
commit 4b976bba6d0389ea9f0edba97c04055f17f47bd7
Author: Reid D McKenzie <me...@arrdem.com>
AuthorDate: Thu Dec 17 11:48:45 2020 -0700
Minor typo (#357)
Just something I noticed while reading the announcement.
Congrats on the release!
---
.../site/content/en/blog/airflow-two-point-oh-is-here/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/landing-pages/site/content/en/blog/airflow-two-point-oh-is-here/index.md b/landing-pages/site/content/en/blog/airflow-two-point-oh-is-here/index.md
index db2ca3c..cb61458 100644
--- a/landing-pages/site/content/en/blog/airflow-two-point-oh-is-here/index.md
+++ b/landing-pages/site/content/en/blog/airflow-two-point-oh-is-here/index.md
@@ -83,7 +83,7 @@ For more information, read the [Scheduler HA documentation](http://airflow.apach
## Task Groups (AIP-34)
-SubDAGs were commonly used for grouping tasks in the UI, but they had many drawbacks in their execution behaviour (primarirly that they only executed a single task in parallel!) To improve this experience, we’ve introduced "Task Groups": a method for organizing tasks which provides the same grouping behaviour as a subdag without any of the execution-time drawbacks.
+SubDAGs were commonly used for grouping tasks in the UI, but they had many drawbacks in their execution behaviour (primarily that they only executed a single task in parallel!) To improve this experience, we’ve introduced "Task Groups": a method for organizing tasks which provides the same grouping behaviour as a subdag without any of the execution-time drawbacks.
SubDAGs will still work for now, but we think that any previous use of SubDAGs can now be replaced with task groups. If you find an example where this isn't the case, please let us know by opening an issue on GitHub