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 2021/08/25 00:02:07 UTC
[beam] branch asf-site updated: Publishing website 2021/08/25
00:01:37 at commit c439abf
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 ce341d7 Publishing website 2021/08/25 00:01:37 at commit c439abf
ce341d7 is described below
commit ce341d74fe2432c0565e378c6b760e25165ea88a
Author: jenkins <bu...@apache.org>
AuthorDate: Wed Aug 25 00:01:38 2021 +0000
Publishing website 2021/08/25 00:01:37 at commit c439abf
---
website/generated-content/documentation/index.xml | 7 +++++++
.../generated-content/documentation/programming-guide/index.html | 6 +++++-
website/generated-content/sitemap.xml | 2 +-
3 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/website/generated-content/documentation/index.xml b/website/generated-content/documentation/index.xml
index 2829227..ca70856 100644
--- a/website/generated-content/documentation/index.xml
+++ b/website/generated-content/documentation/index.xml
@@ -4156,6 +4156,13 @@ express types as a set of named fields, allowing for more-expressive aggregation
individual elements. A Beam Transform might process each element of a
<code>PCollection</code> and generate new pipeline data (as a new <code>PCollection</code>), <em>but it
does not consume or modify the original input collection</em>.</p>
+<blockquote>
+<p><strong>Note:</strong> Beam SDKs avoid unnecessary copying of elements, so <code>PCollection</code>
+contents are logically immutable, not physically immutable. Changes to input
+elements may be visible to other DoFns executing within the same bundle, and may
+cause correctness issues.
+As a rule, it&rsquo;s not safe to modify values provided to a DoFn.</p>
+</blockquote>
<h4 id="random-access">3.2.4. Random access</h4>
<p>A <code>PCollection</code> does not support random access to individual elements. Instead,
Beam Transforms consider every element in a <code>PCollection</code> individually.</p>
diff --git a/website/generated-content/documentation/programming-guide/index.html b/website/generated-content/documentation/programming-guide/index.html
index a969c5a..c1b84aff 100644
--- a/website/generated-content/documentation/programming-guide/index.html
+++ b/website/generated-content/documentation/programming-guide/index.html
@@ -269,7 +269,11 @@ Examples are JSON, Protocol Buffer, Avro, and database records. Schemas provide
express types as a set of named fields, allowing for more-expressive aggregations.</p><h4 id=immutability>3.2.3. Immutability</h4><p>A <code>PCollection</code> is immutable. Once created, you cannot add, remove, or change
individual elements. A Beam Transform might process each element of a
<code>PCollection</code> and generate new pipeline data (as a new <code>PCollection</code>), <em>but it
-does not consume or modify the original input collection</em>.</p><h4 id=random-access>3.2.4. Random access</h4><p>A <code>PCollection</code> does not support random access to individual elements. Instead,
+does not consume or modify the original input collection</em>.</p><blockquote><p><strong>Note:</strong> Beam SDKs avoid unnecessary copying of elements, so <code>PCollection</code>
+contents are logically immutable, not physically immutable. Changes to input
+elements may be visible to other DoFns executing within the same bundle, and may
+cause correctness issues.
+As a rule, it’s not safe to modify values provided to a DoFn.</p></blockquote><h4 id=random-access>3.2.4. Random access</h4><p>A <code>PCollection</code> does not support random access to individual elements. Instead,
Beam Transforms consider every element in a <code>PCollection</code> individually.</p><h4 id=size-and-boundedness>3.2.5. Size and boundedness</h4><p>A <code>PCollection</code> is a large, immutable “bag” of elements. There is no upper limit
on how many elements a <code>PCollection</code> can contain; any given <code>PCollection</code> might
fit in memory on a single machine, or it might represent a very large
diff --git a/website/generated-content/sitemap.xml b/website/generated-content/sitemap.xml
index 5b08961..b0f19d5 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>/blog/beam-2.31.0/</loc><lastmod>2021-06-22T18:45:24-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2021-07-01T15:48:01-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2021-07-01T15:48:01-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2021-07-01T15:48:01-07:00</lastmod></url><url><loc>/blog/b [...]
\ 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>/blog/beam-2.31.0/</loc><lastmod>2021-06-22T18:45:24-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2021-07-01T15:48:01-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2021-07-01T15:48:01-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2021-07-01T15:48:01-07:00</lastmod></url><url><loc>/blog/b [...]
\ No newline at end of file