You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by gi...@apache.org on 2020/09/02 00:09:14 UTC
[beam] branch asf-site updated: Publishing website 2020/09/02
00:09:01 at commit ab597ff
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f9a5c71 Publishing website 2020/09/02 00:09:01 at commit ab597ff
f9a5c71 is described below
commit f9a5c71a02e61f31167b59b6a53ded84976c4127
Author: jenkins <bu...@apache.org>
AuthorDate: Wed Sep 2 00:09:01 2020 +0000
Publishing website 2020/09/02 00:09:01 at commit ab597ff
---
website/generated-content/documentation/index.xml | 4 ++--
website/generated-content/documentation/runtime/model/index.html | 4 ++--
website/generated-content/sitemap.xml | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/website/generated-content/documentation/index.xml b/website/generated-content/documentation/index.xml
index 9851084..6a39ae6 100644
--- a/website/generated-content/documentation/index.xml
+++ b/website/generated-content/documentation/index.xml
@@ -9491,8 +9491,8 @@ figure.</p>
retries the entire bundle.</em></p>
<p>Because we encountered a failure while processing an element in the input
bundle, we had to reprocess <em>all</em> of the elements in the input bundle. This means
-the runner must throw away the entire output bundle since all of the results it
-contains will be recomputed.</p>
+the runner must throw away the entire output of the bundle (including any state
+mutations and set timers) since all of the results it contains will be recomputed.</p>
<p>Note that if the failed transform is a <code>ParDo</code>, then the <code>DoFn</code> instance is torn
down and abandoned.</p>
<h3 id="coupled-failure">Coupled failure: Failures between transforms</h3>
diff --git a/website/generated-content/documentation/runtime/model/index.html b/website/generated-content/documentation/runtime/model/index.html
index ef384a6..02cf221 100644
--- a/website/generated-content/documentation/runtime/model/index.html
+++ b/website/generated-content/documentation/runtime/model/index.html
@@ -58,8 +58,8 @@ happen on the same worker as the original processing attempt, as shown in the
figure.</p><p><img src=/images/execution_model_failure_retry.svg alt="Worker two fails to process an element in bundle B. Worker one finishes processing bundle A and then successfully retries to execute bundle B."></p><p><em>Figure 6: The processing of an element within bundle B fails, and another worker
retries the entire bundle.</em></p><p>Because we encountered a failure while processing an element in the input
bundle, we had to reprocess <em>all</em> of the elements in the input bundle. This means
-the runner must throw away the entire output bundle since all of the results it
-contains will be recomputed.</p><p>Note that if the failed transform is a <code>ParDo</code>, then the <code>DoFn</code> instance is torn
+the runner must throw away the entire output of the bundle (including any state
+mutations and set timers) since all of the results it contains will be recomputed.</p><p>Note that if the failed transform is a <code>ParDo</code>, then the <code>DoFn</code> instance is torn
down and abandoned.</p><h3 id=coupled-failure>Coupled failure: Failures between transforms</h3><p>If a failure to process an element in <code>ParDo2</code> causes <code>ParDo1</code> to re-execute,
these two steps are said to be <em>co-failing</em>.</p><p>For this example, we will use the two <code>ParDo</code>s from figure 4.</p><p>In figure 7, worker two successfully executes <code>ParDo1</code> on all elements in bundle
B. However, the worker fails to process an element in bundle D, so <code>ParDo2</code>
diff --git a/website/generated-content/sitemap.xml b/website/generated-content/sitemap.xml
index 671d19c..cf0cab9 100644
--- a/website/generated-content/sitemap.xml
+++ b/website/generated-content/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>/categories/blog/</loc><lastmod>2020-08-26T13:09:05-05:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-08-26T13:09:05-05:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-08-26T13:09:05-05:00</lastmod></url><url><loc>/blog/python-improved-annotations/</loc><lastmod>2020-08-26T13:09:05-05:00</lastmod></url>< [...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>/categories/blog/</loc><lastmod>2020-08-26T13:09:05-05:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-08-26T13:09:05-05:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-08-26T13:09:05-05:00</lastmod></url><url><loc>/blog/python-improved-annotations/</loc><lastmod>2020-08-26T13:09:05-05:00</lastmod></url>< [...]
\ No newline at end of file