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 e999e30e6e8 Publishing website 2023/01/19 04:15:44 at commit 13a740b
e999e30e6e8 is described below

commit e999e30e6e8a6fcc4175f5f449ac56e936294a20
Author: jenkins <[email protected]>
AuthorDate: Thu Jan 19 04:15:44 2023 +0000

    Publishing website 2023/01/19 04:15:44 at commit 13a740b
---
 website/generated-content/documentation/index.xml                    | 3 ++-
 website/generated-content/documentation/programming-guide/index.html | 5 +++--
 website/generated-content/sitemap.xml                                | 2 +-
 3 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/website/generated-content/documentation/index.xml 
b/website/generated-content/documentation/index.xml
index e211e164fdd..29195b9966c 100644
--- a/website/generated-content/documentation/index.xml
+++ b/website/generated-content/documentation/index.xml
@@ -5886,7 +5886,8 @@ from the input collection; the Beam SDKs handle that for 
you. Your &lt;code>proc
 should accept an argument &lt;code>element&lt;/code>, which is the input 
element, and return an
 iterable with its output values. You can accomplish this by emitting individual
 elements with &lt;code>yield&lt;/code> statements. You can also use a 
&lt;code>return&lt;/code> statement
-with an iterable, like a list or a generator.&lt;/p>
+with an iterable, like a list or a generator. Don&amp;rsquo;t mix 
&lt;code>yield&lt;/code> and
+&lt;code>return&lt;/code> statements in the same &lt;code>process&lt;/code> 
method - this leads to &lt;a 
href="https://github.com/apache/beam/issues/22969";>undefined 
behavior&lt;/a>.&lt;/p>
 &lt;p class="language-go">For your &lt;code>DoFn&lt;/code> type, 
you&amp;rsquo;ll write a method &lt;code>ProcessElement&lt;/code> where you 
provide
 the actual processing logic. You don&amp;rsquo;t need to manually extract the 
elements
 from the input collection; the Beam SDKs handle that for you. Your 
&lt;code>ProcessElement&lt;/code> method
diff --git 
a/website/generated-content/documentation/programming-guide/index.html 
b/website/generated-content/documentation/programming-guide/index.html
index e4b40e2713e..9b9e1d3130f 100644
--- a/website/generated-content/documentation/programming-guide/index.html
+++ b/website/generated-content/documentation/programming-guide/index.html
@@ -571,7 +571,8 @@ from the input collection; the Beam SDKs handle that for 
you. Your <code>process
 should accept an argument <code>element</code>, which is the input element, 
and return an
 iterable with its output values. You can accomplish this by emitting individual
 elements with <code>yield</code> statements. You can also use a 
<code>return</code> statement
-with an iterable, like a list or a generator.</p><p class=language-go>For your 
<code>DoFn</code> type, you&rsquo;ll write a method <code>ProcessElement</code> 
where you provide
+with an iterable, like a list or a generator. Don&rsquo;t mix 
<code>yield</code> and
+<code>return</code> statements in the same <code>process</code> method - this 
leads to <a href=https://github.com/apache/beam/issues/22969>undefined 
behavior</a>.</p><p class=language-go>For your <code>DoFn</code> type, 
you&rsquo;ll write a method <code>ProcessElement</code> where you provide
 the actual processing logic. You don&rsquo;t need to manually extract the 
elements
 from the input collection; the Beam SDKs handle that for you. Your 
<code>ProcessElement</code> method
 should accept a parameter <code>element</code>, which is the input element. In 
order to output elements,
@@ -5271,7 +5272,7 @@ implementations. This information can be accessed by 
using the conventional
      <span class=o>...</span>
 
   <span class=k>def</span> <span class=nf>infer_output_type</span><span 
class=p>(</span><span class=bp>self</span><span class=p>,</span> <span 
class=n>input_type</span><span class=p>):</span>
-    <span class=k>return</span> <span 
class=n>input_type</span></code></pre></div></div></div><div class=feedback><p 
class=update>Last updated on 2023/01/04</p><h3>Have you found everything you 
were looking for?</h3><p class=description>Was it all useful and clear? Is 
there anything that you would like to change? Let us know!</p><button 
class=load-button><a href="mailto:[email protected]?subject=Beam Website 
Feedback">SEND FEEDBACK</a></button></div></div></div><footer class=footer><di 
[...]
+    <span class=k>return</span> <span 
class=n>input_type</span></code></pre></div></div></div><div class=feedback><p 
class=update>Last updated on 2023/01/18</p><h3>Have you found everything you 
were looking for?</h3><p class=description>Was it all useful and clear? Is 
there anything that you would like to change? Let us know!</p><button 
class=load-button><a href="mailto:[email protected]?subject=Beam Website 
Feedback">SEND FEEDBACK</a></button></div></div></div><footer class=footer><di 
[...]
 <a href=https://www.apache.org>The Apache Software Foundation</a>
 | <a href=/privacy_policy>Privacy Policy</a>
 | <a href=/feed.xml>RSS Feed</a><br><br>Apache Beam, Apache, Beam, the Beam 
logo, and the Apache feather logo are either registered trademarks or 
trademarks of The Apache Software Foundation. All other products or name brands 
are trademarks of their respective holders, including The Apache Software 
Foundation.</div></div><div class="footer__cols__col 
footer__cols__col__logos"><div class=footer__cols__col--group><div 
class=footer__cols__col__logo><a href=https://github.com/apache/beam><im [...]
\ No newline at end of file
diff --git a/website/generated-content/sitemap.xml 
b/website/generated-content/sitemap.xml
index 3f5bac3ca1a..a04b51dfeb3 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.44.0/</loc><lastmod>2023-01-18T12:23:16-05:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-01-18T12:23:16-05:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-01-18T12:23:16-05:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-01-18T12:23:16-05:00</lastmod></url><url><loc>/catego
 [...]
\ 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.44.0/</loc><lastmod>2023-01-18T12:23:16-05:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-01-18T12:23:16-05:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-01-18T12:23:16-05:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-01-18T12:23:16-05:00</lastmod></url><url><loc>/catego
 [...]
\ No newline at end of file

Reply via email to