This is an automated email from the ASF dual-hosted git repository.
kaxilnaik pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/airflow-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1b9c0a9 Update - Fri 10 Apr 2020 18:33:19 BST
1b9c0a9 is described below
commit 1b9c0a999c9fd199ff5835d8f63e91410e238d41
Author: Kaxil Naik <[email protected]>
AuthorDate: Fri Apr 10 18:33:19 2020 +0100
Update - Fri 10 Apr 2020 18:33:19 BST
---
_gen/indexes/en/blog-index.json | 2 +-
_gen/indexes/en/blog-posts.json | 2 +-
blog/airflow-1.10.10/index.html | 48 ++++++++++++++++++++++++++----
blog/airflow-1.10.10/trigger-dag-conf.png | Bin 0 -> 157871 bytes
blog/index.xml | 42 ++++++++++++++++++++++++--
blog/tags/release/index.xml | 42 ++++++++++++++++++++++++--
index.html | 30 +++++++++----------
index.xml | 42 ++++++++++++++++++++++++--
sitemap.xml | 6 ++--
9 files changed, 183 insertions(+), 31 deletions(-)
diff --git a/_gen/indexes/en/blog-index.json b/_gen/indexes/en/blog-index.json
index 324f03c..dd2a336 100644
--- a/_gen/indexes/en/blog-index.json
+++ b/_gen/indexes/en/blog-index.json
@@ -1 +1 @@
-{"version":"2.3.8","fields":["title","description","author","content","tags","url"],"fieldVectors":[["title/It's
a \"Breeze\" to develop Apache
Airflow",[0,1.805,1,0.76,2,0.219,3,0.339,4,0.469]],["description/It's a
\"Breeze\" to develop Apache
Airflow",[2,0.236,4,0.329,5,1.268,6,0.534,7,1.268,8,0.702,9,0.534,10,0.702,11,0.534,12,0.4,13,1.268,14,0.4,15,1.268,16,0.034]],["author/It's
a \"Breeze\" to develop Apache Airflow",[11,0.76,17,0.999]],["content/It's a
\"Breeze\" to develop Apache [...]
\ No newline at end of file
+{"version":"2.3.8","fields":["title","description","author","content","tags","url"],"fieldVectors":[["title/It's
a \"Breeze\" to develop Apache
Airflow",[0,1.805,1,0.76,2,0.219,3,0.339,4,0.469]],["description/It's a
\"Breeze\" to develop Apache
Airflow",[2,0.236,4,0.329,5,1.268,6,0.534,7,1.268,8,0.702,9,0.534,10,0.702,11,0.534,12,0.4,13,1.268,14,0.4,15,1.268,16,0.034]],["author/It's
a \"Breeze\" to develop Apache Airflow",[11,0.76,17,0.999]],["content/It's a
\"Breeze\" to develop Apache [...]
\ No newline at end of file
diff --git a/_gen/indexes/en/blog-posts.json b/_gen/indexes/en/blog-posts.json
index 5296dd0..47195c0 100644
--- a/_gen/indexes/en/blog-posts.json
+++ b/_gen/indexes/en/blog-posts.json
@@ -1 +1 @@
-[{"content":"## The story behind the Airflow Breeze tool\nInitially, we
started contributing to this fantastic open-source project [Apache Airflow]
with a team of three which then grew to five. When we kicked it off a year ago,
I realized pretty soon where the biggest bottlenecks and areas for improvement
in terms of productivity were. Even with the help of our client, who provided
us with a “homegrown” development environment it took us literally days to set
it up and learn some basics. [...]
\ No newline at end of file
+[{"content":"## The story behind the Airflow Breeze tool\nInitially, we
started contributing to this fantastic open-source project [Apache Airflow]
with a team of three which then grew to five. When we kicked it off a year ago,
I realized pretty soon where the biggest bottlenecks and areas for improvement
in terms of productivity were. Even with the help of our client, who provided
us with a “homegrown” development environment it took us literally days to set
it up and learn some basics. [...]
\ No newline at end of file
diff --git a/blog/airflow-1.10.10/index.html b/blog/airflow-1.10.10/index.html
index d5f2b68..779138e 100644
--- a/blog/airflow-1.10.10/index.html
+++ b/blog/airflow-1.10.10/index.html
@@ -36,14 +36,14 @@
<meta property="og:image" content="/images/feature-image.png" />
<meta property="article:published_time" content="2020-04-09T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-04-10T16:45:22+01:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-04-10T18:23:27+01:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 1.10.10">
<meta itemprop="description" content="We are happy to present Apache Airflow
1.10.10">
<meta itemprop="datePublished" content="2020-04-09T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2020-04-10T16:45:22+01:00" />
-<meta itemprop="wordCount" content="883">
+<meta itemprop="dateModified" content="2020-04-10T18:23:27+01:00" />
+<meta itemprop="wordCount" content="1138">
@@ -444,13 +444,15 @@ if (!doNotTrack) {
<li><strong>Changelog</strong>: <a
href="http://airflow.apache.org/docs/1.10.10/changelog.html";
target="_blank">http://airflow.apache.org/docs/1.10.10/changelog.html</a></li>
</ul>
-<p>Some of the noteworthy new features (user-facing) are:</p>
+<p>Some of the noteworthy new features & improvements are:</p>
<ul>
<li><a href="https://github.com/apache/airflow/pull/8046";
target="_blank">Allow user to chose timezone to use in the RBAC UI</a></li>
<li><a href="https://github.com/apache/airflow/pull/7832"; target="_blank">Add
Production Docker image support</a></li>
<li><a
href="http://airflow.apache.org/docs/1.10.10/howto/use-alternative-secrets-backend.html";
target="_blank">Allow Retrieving Airflow Connections & Variables from
various Secrets backend</a></li>
<li><a href="http://airflow.apache.org/docs/1.10.10/dag-serialization.html";
target="_blank">Stateless Webserver using DAG Serialization</a></li>
+<li><a href="https://github.com/apache/airflow/pull/7880";
target="_blank">Dummy Operators are no longer sent to executor</a></li>
+<li><a href="https://github.com/apache/airflow/pull/6256";
target="_blank">Allow passing DagRun conf when triggering dags via UI</a></li>
</ul>
<h3 id="allow-user-to-chose-timezone-to-use-in-the-rbac-ui">Allow user to
chose timezone to use in the RBAC UI</h3>
@@ -515,6 +517,42 @@ backend =
airflow.contrib.secrets.hashicorp_vault.VaultBackend
backend_kwargs = {"url": "http://127.0.0.1:8200",
"connections_path": "connections",
"variables_path": "variables", "mount_point":
"airflow"}
</code></pre>
+<h3 id="stateless-webserver-using-dag-serialization">Stateless Webserver using
DAG Serialization</h3>
+
+<p>The Webserver can now run without access to DAG Files when DAG
Serialization is turned on.
+The 2 limitations we had in 1.10.7-1.10.9 (
+<a
href="https://airflow.apache.org/docs/1.10.7/dag-serialization.html#limitations)"
target="_blank">https://airflow.apache.org/docs/1.10.7/dag-serialization.html#limitations)</a>
+have been resolved.</p>
+
+<p>The main advantage of this would be reduction in Webserver startup time for
large number of DAGs.
+Without DAG Serialization all the DAGs are loaded in the DagBag during the
+Webserver startup.</p>
+
+<p>With DAG Serialization, an empty DagBag is created and
+Dags are loaded from DB only when needed (i.e. when a particular DAG is
+clicked on in the home page)</p>
+
+<p>Details: <a
href="http://airflow.apache.org/docs/1.10.10/dag-serialization.html";
target="_blank">http://airflow.apache.org/docs/1.10.10/dag-serialization.html</a></p>
+
+<h3 id="dummy-operators-are-no-longer-sent-to-executor">Dummy Operators are no
longer sent to executor</h3>
+
+<p>The Dummy operators does not actually do any work and are mostly used for
organizing/grouping tasks along
+with BranchPythonOperator.</p>
+
+<p>Previously, when using Kubernetes Executor, the executor would spin up a
whole worker pod to execute a dummy task.
+With Airflow 1.10.10 tasks using Dummy Operators would be scheduled &
evaluated by the Scheduler but not sent to the
+Executor. This should significantly improve execution time and resource
usage.</p>
+
+<h3 id="allow-passing-dagrun-conf-when-triggering-dags-via-ui">Allow passing
DagRun conf when triggering dags via UI</h3>
+
+<p>When triggering a DAG from the CLI or the REST API, it s possible to pass
configuration for the DAG run as a JSON blob.</p>
+
+<p>From Airflow 1.10.10, when a user clicks on Trigger Dag button, a new
screen confirming the trigger request, and allowing the user to pass a JSON
configuration
+blob would be show.</p>
+
+<p><strong>Screenshot</strong>:
+<img src="trigger-dag-conf.png" alt="Allow passing DagRun conf when triggering
dags via UI" /></p>
+
<h2 id="updating-guide">Updating Guide</h2>
<p>If you are updating Apache Airflow from a previous version to
<code>1.10.10</code>, please take a note of the following:</p>
@@ -555,7 +593,7 @@ Airflow 1.10.* would be the last series to support Python
2.</p>
<p>Airflow 1.10.10 ships with 2 UIs, the default is non-RBAC Flask-admin based
UI and Flask-appbuilder based UI.</p>
-<p>The Flask-AppBuilder (FAB) based UI is allows Role-based Access Control and
has more advanced features compared to
+<p>The Flask-AppBuilder (FAB) based UI allows Role-based Access Control and
has more advanced features compared to
the legacy Flask-admin based UI. This UI can be enabled by setting
<code>rbac=True</code> in <code>[webserver]</code> section in your
<code>airflow.cfg</code>.</p>
<p>Flask-admin based UI is deprecated and new features won’t be ported
to it. This UI will still be the default
diff --git a/blog/airflow-1.10.10/trigger-dag-conf.png
b/blog/airflow-1.10.10/trigger-dag-conf.png
new file mode 100644
index 0000000..40f1f54
Binary files /dev/null and b/blog/airflow-1.10.10/trigger-dag-conf.png differ
diff --git a/blog/index.xml b/blog/index.xml
index 55dc4bf..4708222 100644
--- a/blog/index.xml
+++ b/blog/index.xml
@@ -34,13 +34,15 @@
<li><strong>Changelog</strong>: <a
href="http://airflow.apache.org/docs/1.10.10/changelog.html"
target="_blank">http://airflow.apache.org/docs/1.10.10/changelog.html</a></li>
</ul>
-<p>Some of the noteworthy new features (user-facing) are:</p>
+<p>Some of the noteworthy new features &amp; improvements
are:</p>
<ul>
<li><a href="https://github.com/apache/airflow/pull/8046"
target="_blank">Allow user to chose timezone to use in the RBAC
UI</a></li>
<li><a href="https://github.com/apache/airflow/pull/7832"
target="_blank">Add Production Docker image
support</a></li>
<li><a
href="http://airflow.apache.org/docs/1.10.10/howto/use-alternative-secrets-backend.html"
target="_blank">Allow Retrieving Airflow Connections &amp;
Variables from various Secrets backend</a></li>
<li><a
href="http://airflow.apache.org/docs/1.10.10/dag-serialization.html"
target="_blank">Stateless Webserver using DAG
Serialization</a></li>
+<li><a href="https://github.com/apache/airflow/pull/7880"
target="_blank">Dummy Operators are no longer sent to
executor</a></li>
+<li><a href="https://github.com/apache/airflow/pull/6256"
target="_blank">Allow passing DagRun conf when triggering dags via
UI</a></li>
</ul>
<h3
id="allow-user-to-chose-timezone-to-use-in-the-rbac-ui">Allow user
to chose timezone to use in the RBAC UI</h3>
@@ -105,6 +107,42 @@ backend =
airflow.contrib.secrets.hashicorp_vault.VaultBackend
backend_kwargs = {&quot;url&quot;:
&quot;http://127.0.0.1:8200&quot;,
&quot;connections_path&quot;: &quot;connections&quot;,
&quot;variables_path&quot;: &quot;variables&quot;,
&quot;mount_point&quot;: &quot;airflow&quot;}
</code></pre>
+<h3 id="stateless-webserver-using-dag-serialization">Stateless
Webserver using DAG Serialization</h3>
+
+<p>The Webserver can now run without access to DAG Files when DAG
Serialization is turned on.
+The 2 limitations we had in 1.10.7-1.10.9 (
+<a
href="https://airflow.apache.org/docs/1.10.7/dag-serialization.html#limitations)"
target="_blank">https://airflow.apache.org/docs/1.10.7/dag-serialization.html#limitations)</a>
+have been resolved.</p>
+
+<p>The main advantage of this would be reduction in Webserver startup
time for large number of DAGs.
+Without DAG Serialization all the DAGs are loaded in the DagBag during the
+Webserver startup.</p>
+
+<p>With DAG Serialization, an empty DagBag is created and
+Dags are loaded from DB only when needed (i.e. when a particular DAG is
+clicked on in the home page)</p>
+
+<p>Details: <a
href="http://airflow.apache.org/docs/1.10.10/dag-serialization.html"
target="_blank">http://airflow.apache.org/docs/1.10.10/dag-serialization.html</a></p>
+
+<h3 id="dummy-operators-are-no-longer-sent-to-executor">Dummy
Operators are no longer sent to executor</h3>
+
+<p>The Dummy operators does not actually do any work and are mostly used
for organizing/grouping tasks along
+with BranchPythonOperator.</p>
+
+<p>Previously, when using Kubernetes Executor, the executor would spin
up a whole worker pod to execute a dummy task.
+With Airflow 1.10.10 tasks using Dummy Operators would be scheduled &amp;
evaluated by the Scheduler but not sent to the
+Executor. This should significantly improve execution time and resource
usage.</p>
+
+<h3
id="allow-passing-dagrun-conf-when-triggering-dags-via-ui">Allow
passing DagRun conf when triggering dags via UI</h3>
+
+<p>When triggering a DAG from the CLI or the REST API, it s possible to
pass configuration for the DAG run as a JSON blob.</p>
+
+<p>From Airflow 1.10.10, when a user clicks on Trigger Dag button, a new
screen confirming the trigger request, and allowing the user to pass a JSON
configuration
+blob would be show.</p>
+
+<p><strong>Screenshot</strong>:
+<img src="trigger-dag-conf.png" alt="Allow passing DagRun conf
when triggering dags via UI" /></p>
+
<h2 id="updating-guide">Updating Guide</h2>
<p>If you are updating Apache Airflow from a previous version to
<code>1.10.10</code>, please take a note of the following:</p>
@@ -145,7 +183,7 @@ Airflow 1.10.* would be the last series to support Python
2.</p>
<p>Airflow 1.10.10 ships with 2 UIs, the default is non-RBAC Flask-admin
based UI and Flask-appbuilder based UI.</p>
-<p>The Flask-AppBuilder (FAB) based UI is allows Role-based Access
Control and has more advanced features compared to
+<p>The Flask-AppBuilder (FAB) based UI allows Role-based Access Control
and has more advanced features compared to
the legacy Flask-admin based UI. This UI can be enabled by setting
<code>rbac=True</code> in <code>[webserver]</code>
section in your <code>airflow.cfg</code>.</p>
<p>Flask-admin based UI is deprecated and new features won&rsquo;t
be ported to it. This UI will still be the default
diff --git a/blog/tags/release/index.xml b/blog/tags/release/index.xml
index c9b1620..9431b4b 100644
--- a/blog/tags/release/index.xml
+++ b/blog/tags/release/index.xml
@@ -35,13 +35,15 @@
<li><strong>Changelog</strong>: <a
href="http://airflow.apache.org/docs/1.10.10/changelog.html"
target="_blank">http://airflow.apache.org/docs/1.10.10/changelog.html</a></li>
</ul>
-<p>Some of the noteworthy new features (user-facing) are:</p>
+<p>Some of the noteworthy new features &amp; improvements
are:</p>
<ul>
<li><a href="https://github.com/apache/airflow/pull/8046"
target="_blank">Allow user to chose timezone to use in the RBAC
UI</a></li>
<li><a href="https://github.com/apache/airflow/pull/7832"
target="_blank">Add Production Docker image
support</a></li>
<li><a
href="http://airflow.apache.org/docs/1.10.10/howto/use-alternative-secrets-backend.html"
target="_blank">Allow Retrieving Airflow Connections &amp;
Variables from various Secrets backend</a></li>
<li><a
href="http://airflow.apache.org/docs/1.10.10/dag-serialization.html"
target="_blank">Stateless Webserver using DAG
Serialization</a></li>
+<li><a href="https://github.com/apache/airflow/pull/7880"
target="_blank">Dummy Operators are no longer sent to
executor</a></li>
+<li><a href="https://github.com/apache/airflow/pull/6256"
target="_blank">Allow passing DagRun conf when triggering dags via
UI</a></li>
</ul>
<h3
id="allow-user-to-chose-timezone-to-use-in-the-rbac-ui">Allow user
to chose timezone to use in the RBAC UI</h3>
@@ -106,6 +108,42 @@ backend =
airflow.contrib.secrets.hashicorp_vault.VaultBackend
backend_kwargs = {&quot;url&quot;:
&quot;http://127.0.0.1:8200&quot;,
&quot;connections_path&quot;: &quot;connections&quot;,
&quot;variables_path&quot;: &quot;variables&quot;,
&quot;mount_point&quot;: &quot;airflow&quot;}
</code></pre>
+<h3 id="stateless-webserver-using-dag-serialization">Stateless
Webserver using DAG Serialization</h3>
+
+<p>The Webserver can now run without access to DAG Files when DAG
Serialization is turned on.
+The 2 limitations we had in 1.10.7-1.10.9 (
+<a
href="https://airflow.apache.org/docs/1.10.7/dag-serialization.html#limitations)"
target="_blank">https://airflow.apache.org/docs/1.10.7/dag-serialization.html#limitations)</a>
+have been resolved.</p>
+
+<p>The main advantage of this would be reduction in Webserver startup
time for large number of DAGs.
+Without DAG Serialization all the DAGs are loaded in the DagBag during the
+Webserver startup.</p>
+
+<p>With DAG Serialization, an empty DagBag is created and
+Dags are loaded from DB only when needed (i.e. when a particular DAG is
+clicked on in the home page)</p>
+
+<p>Details: <a
href="http://airflow.apache.org/docs/1.10.10/dag-serialization.html"
target="_blank">http://airflow.apache.org/docs/1.10.10/dag-serialization.html</a></p>
+
+<h3 id="dummy-operators-are-no-longer-sent-to-executor">Dummy
Operators are no longer sent to executor</h3>
+
+<p>The Dummy operators does not actually do any work and are mostly used
for organizing/grouping tasks along
+with BranchPythonOperator.</p>
+
+<p>Previously, when using Kubernetes Executor, the executor would spin
up a whole worker pod to execute a dummy task.
+With Airflow 1.10.10 tasks using Dummy Operators would be scheduled &amp;
evaluated by the Scheduler but not sent to the
+Executor. This should significantly improve execution time and resource
usage.</p>
+
+<h3
id="allow-passing-dagrun-conf-when-triggering-dags-via-ui">Allow
passing DagRun conf when triggering dags via UI</h3>
+
+<p>When triggering a DAG from the CLI or the REST API, it s possible to
pass configuration for the DAG run as a JSON blob.</p>
+
+<p>From Airflow 1.10.10, when a user clicks on Trigger Dag button, a new
screen confirming the trigger request, and allowing the user to pass a JSON
configuration
+blob would be show.</p>
+
+<p><strong>Screenshot</strong>:
+<img src="trigger-dag-conf.png" alt="Allow passing DagRun conf
when triggering dags via UI" /></p>
+
<h2 id="updating-guide">Updating Guide</h2>
<p>If you are updating Apache Airflow from a previous version to
<code>1.10.10</code>, please take a note of the following:</p>
@@ -146,7 +184,7 @@ Airflow 1.10.* would be the last series to support Python
2.</p>
<p>Airflow 1.10.10 ships with 2 UIs, the default is non-RBAC Flask-admin
based UI and Flask-appbuilder based UI.</p>
-<p>The Flask-AppBuilder (FAB) based UI is allows Role-based Access
Control and has more advanced features compared to
+<p>The Flask-AppBuilder (FAB) based UI allows Role-based Access Control
and has more advanced features compared to
the legacy Flask-admin based UI. This UI can be enabled by setting
<code>rbac=True</code> in <code>[webserver]</code>
section in your <code>airflow.cfg</code>.</p>
<p>Flask-admin based UI is deprecated and new features won&rsquo;t
be ported to it. This UI will still be the default
diff --git a/index.html b/index.html
index 6288f21..224d5f7 100644
--- a/index.html
+++ b/index.html
@@ -1170,12 +1170,12 @@ if (!doNotTrack) {
<div id="integrations-container" class="list-items">
- <a class="list-item"
href="/docs/stable/integration.html#protocol-integrations">
+ <a class="list-item"
href="/docs/stable/integration.html#aws-amazon-web-services">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">File Transfer Protocol
(FTP)</span>
+ <span class="box-event__integration--name">Amazon DynamoDB</span>
</div>
</div>
@@ -1188,7 +1188,7 @@ if (!doNotTrack) {
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Python</span>
+ <span class="box-event__integration--name">Papermill</span>
</div>
</div>
@@ -1196,12 +1196,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/stable/integration.html#gcp-google-cloud-platform">
+ <a class="list-item"
href="/docs/stable/integration.html#software-integrations">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Cloud Vision</span>
+ <span class="box-event__integration--name">Redis</span>
</div>
</div>
@@ -1209,12 +1209,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/stable/integration.html#asf-apache-software-foundation">
+ <a class="list-item"
href="/docs/stable/integration.html#aws-amazon-web-services">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Hadoop Distributed File
System (HDFS)</span>
+ <span class="box-event__integration--name">Amazon Simple Storage
Service (S3)</span>
</div>
</div>
@@ -1222,12 +1222,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/stable/integration.html#asf-apache-software-foundation">
+ <a class="list-item"
href="/docs/stable/integration.html#service-integrations">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Apache Pinot</span>
+ <span class="box-event__integration--name">Google Display&Video
360</span>
</div>
</div>
@@ -1235,12 +1235,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/stable/integration.html#azure-microsoft-azure">
+ <a class="list-item"
href="/docs/stable/integration.html#gcp-google-cloud-platform">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Azure Data Lake
Storage</span>
+ <span class="box-event__integration--name">Cloud Memorystore</span>
</div>
</div>
@@ -1248,12 +1248,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/stable/integration.html#aws-amazon-web-services">
+ <a class="list-item"
href="/docs/stable/integration.html#protocol-integrations">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Amazon Simple Notification
Service (SNS)</span>
+ <span class="box-event__integration--name">Internet Message Access
Protocol (IMAP)</span>
</div>
</div>
@@ -1261,12 +1261,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/stable/integration.html#gcp-google-cloud-platform">
+ <a class="list-item"
href="/docs/stable/integration.html#protocol-integrations">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Cloud Spanner</span>
+ <span class="box-event__integration--name">Windows Remote Management
(WinRM)</span>
</div>
</div>
diff --git a/index.xml b/index.xml
index 0467730..a60c6ac 100644
--- a/index.xml
+++ b/index.xml
@@ -33,13 +33,15 @@
<li><strong>Changelog</strong>: <a
href="http://airflow.apache.org/docs/1.10.10/changelog.html"
target="_blank">http://airflow.apache.org/docs/1.10.10/changelog.html</a></li>
</ul>
-<p>Some of the noteworthy new features (user-facing) are:</p>
+<p>Some of the noteworthy new features &amp; improvements
are:</p>
<ul>
<li><a href="https://github.com/apache/airflow/pull/8046"
target="_blank">Allow user to chose timezone to use in the RBAC
UI</a></li>
<li><a href="https://github.com/apache/airflow/pull/7832"
target="_blank">Add Production Docker image
support</a></li>
<li><a
href="http://airflow.apache.org/docs/1.10.10/howto/use-alternative-secrets-backend.html"
target="_blank">Allow Retrieving Airflow Connections &amp;
Variables from various Secrets backend</a></li>
<li><a
href="http://airflow.apache.org/docs/1.10.10/dag-serialization.html"
target="_blank">Stateless Webserver using DAG
Serialization</a></li>
+<li><a href="https://github.com/apache/airflow/pull/7880"
target="_blank">Dummy Operators are no longer sent to
executor</a></li>
+<li><a href="https://github.com/apache/airflow/pull/6256"
target="_blank">Allow passing DagRun conf when triggering dags via
UI</a></li>
</ul>
<h3
id="allow-user-to-chose-timezone-to-use-in-the-rbac-ui">Allow user
to chose timezone to use in the RBAC UI</h3>
@@ -104,6 +106,42 @@ backend =
airflow.contrib.secrets.hashicorp_vault.VaultBackend
backend_kwargs = {&quot;url&quot;:
&quot;http://127.0.0.1:8200&quot;,
&quot;connections_path&quot;: &quot;connections&quot;,
&quot;variables_path&quot;: &quot;variables&quot;,
&quot;mount_point&quot;: &quot;airflow&quot;}
</code></pre>
+<h3 id="stateless-webserver-using-dag-serialization">Stateless
Webserver using DAG Serialization</h3>
+
+<p>The Webserver can now run without access to DAG Files when DAG
Serialization is turned on.
+The 2 limitations we had in 1.10.7-1.10.9 (
+<a
href="https://airflow.apache.org/docs/1.10.7/dag-serialization.html#limitations)"
target="_blank">https://airflow.apache.org/docs/1.10.7/dag-serialization.html#limitations)</a>
+have been resolved.</p>
+
+<p>The main advantage of this would be reduction in Webserver startup
time for large number of DAGs.
+Without DAG Serialization all the DAGs are loaded in the DagBag during the
+Webserver startup.</p>
+
+<p>With DAG Serialization, an empty DagBag is created and
+Dags are loaded from DB only when needed (i.e. when a particular DAG is
+clicked on in the home page)</p>
+
+<p>Details: <a
href="http://airflow.apache.org/docs/1.10.10/dag-serialization.html"
target="_blank">http://airflow.apache.org/docs/1.10.10/dag-serialization.html</a></p>
+
+<h3 id="dummy-operators-are-no-longer-sent-to-executor">Dummy
Operators are no longer sent to executor</h3>
+
+<p>The Dummy operators does not actually do any work and are mostly used
for organizing/grouping tasks along
+with BranchPythonOperator.</p>
+
+<p>Previously, when using Kubernetes Executor, the executor would spin
up a whole worker pod to execute a dummy task.
+With Airflow 1.10.10 tasks using Dummy Operators would be scheduled &amp;
evaluated by the Scheduler but not sent to the
+Executor. This should significantly improve execution time and resource
usage.</p>
+
+<h3
id="allow-passing-dagrun-conf-when-triggering-dags-via-ui">Allow
passing DagRun conf when triggering dags via UI</h3>
+
+<p>When triggering a DAG from the CLI or the REST API, it s possible to
pass configuration for the DAG run as a JSON blob.</p>
+
+<p>From Airflow 1.10.10, when a user clicks on Trigger Dag button, a new
screen confirming the trigger request, and allowing the user to pass a JSON
configuration
+blob would be show.</p>
+
+<p><strong>Screenshot</strong>:
+<img src="trigger-dag-conf.png" alt="Allow passing DagRun conf
when triggering dags via UI" /></p>
+
<h2 id="updating-guide">Updating Guide</h2>
<p>If you are updating Apache Airflow from a previous version to
<code>1.10.10</code>, please take a note of the following:</p>
@@ -144,7 +182,7 @@ Airflow 1.10.* would be the last series to support Python
2.</p>
<p>Airflow 1.10.10 ships with 2 UIs, the default is non-RBAC Flask-admin
based UI and Flask-appbuilder based UI.</p>
-<p>The Flask-AppBuilder (FAB) based UI is allows Role-based Access
Control and has more advanced features compared to
+<p>The Flask-AppBuilder (FAB) based UI allows Role-based Access Control
and has more advanced features compared to
the legacy Flask-admin based UI. This UI can be enabled by setting
<code>rbac=True</code> in <code>[webserver]</code>
section in your <code>airflow.cfg</code>.</p>
<p>Flask-admin based UI is deprecated and new features won&rsquo;t
be ported to it. This UI will still be the default
diff --git a/sitemap.xml b/sitemap.xml
index aab3516..d1a85f9 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -84,17 +84,17 @@
<url>
<loc>/blog/airflow-1.10.10/</loc>
- <lastmod>2020-04-10T16:45:22+01:00</lastmod>
+ <lastmod>2020-04-10T18:23:27+01:00</lastmod>
</url>
<url>
<loc>/blog/tags/release/</loc>
- <lastmod>2020-04-10T16:45:22+01:00</lastmod>
+ <lastmod>2020-04-10T18:23:27+01:00</lastmod>
</url>
<url>
<loc>/tags/</loc>
- <lastmod>2020-04-10T16:45:22+01:00</lastmod>
+ <lastmod>2020-04-10T18:23:27+01:00</lastmod>
</url>
<url>
