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 08de4352b33 Publishing website 2023/03/30 04:15:30 at commit d9321d8 08de4352b33 is described below commit 08de4352b3335839e9d24bd4cb515bc2f01558e5 Author: jenkins <bui...@apache.org> AuthorDate: Thu Mar 30 04:15:30 2023 +0000 Publishing website 2023/03/30 04:15:30 at commit d9321d8 --- website/generated-content/documentation/index.xml | 7 ++++--- .../generated-content/documentation/programming-guide/index.html | 7 ++++--- website/generated-content/sitemap.xml | 2 +- 3 files changed, 9 insertions(+), 7 deletions(-) diff --git a/website/generated-content/documentation/index.xml b/website/generated-content/documentation/index.xml index b868dca5e43..d71a2d526b7 100644 --- a/website/generated-content/documentation/index.xml +++ b/website/generated-content/documentation/index.xml @@ -6036,9 +6036,10 @@ the actual processing logic. You don&rsquo;t need to manually extract the el from the input collection; the Beam SDKs handle that for you. Your <code>process</code> method 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. 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> +elements with <code>yield</code> statements, and use <code>yield from</code> to emit all elements from +an iterable, such as a list or a generator. Using <code>return</code> statement +with an iterable is also acceptable as long as you don&rsquo;t mix <code>yield</code> and +<code>return</code> statements in the same <code>process</code> method, since that leads to <a href="https://github.com/apache/beam/issues/22969">incorrect 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 diff --git a/website/generated-content/documentation/programming-guide/index.html b/website/generated-content/documentation/programming-guide/index.html index c682df5877b..d33e1d25237 100644 --- a/website/generated-content/documentation/programming-guide/index.html +++ b/website/generated-content/documentation/programming-guide/index.html @@ -571,9 +571,10 @@ the actual processing logic. You don’t need to manually extract the elemen from the input collection; the Beam SDKs handle that for you. Your <code>process</code> method 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. Don’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’ll write a method <code>ProcessElement</code> where you provide +elements with <code>yield</code> statements, and use <code>yield from</code> to emit all elements from +an iterable, such as a list or a generator. Using <code>return</code> statement +with an iterable is also acceptable as long as you don’t mix <code>yield</code> and +<code>return</code> statements in the same <code>process</code> method, since that leads to <a href=https://github.com/apache/beam/issues/22969>incorrect behavior</a>.</p><p class=language-go>For your <code>DoFn</code> type, you’ll write a method <code>ProcessElement</code> where you provide the actual processing logic. You don’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, diff --git a/website/generated-content/sitemap.xml b/website/generated-content/sitemap.xml index 39362c7fa06..e5af00de780 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.46.0/</loc><lastmod>2023-03-29T14:08:31-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-03-29T14:08:31-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-03-29T14:08:31-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-03-29T14:08:31-07: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.46.0/</loc><lastmod>2023-03-29T17:16:24-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-03-29T17:16:24-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-03-29T17:16:24-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-03-29T17:16:24-07:00</lastmod></url><url><loc>/catego [...] \ No newline at end of file