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 bfb2b68d5f3 Publishing website 2023/04/05 22:17:23 at commit f1abd75
bfb2b68d5f3 is described below
commit bfb2b68d5f319c4444c02e172af8e9ac68ee059c
Author: jenkins <[email protected]>
AuthorDate: Wed Apr 5 22:17:23 2023 +0000
Publishing website 2023/04/05 22:17:23 at commit f1abd75
---
website/generated-content/contribute/index.xml | 11 ++++++++---
.../generated-content/contribute/release-guide/index.html | 12 ++++++++----
website/generated-content/documentation/index.xml | 7 +++++--
.../documentation/programming-guide/index.html | 7 +++++--
website/generated-content/sitemap.xml | 2 +-
5 files changed, 27 insertions(+), 12 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index d08a182aa35..c807b0585e1 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -902,7 +902,7 @@ If you need one, <a
href="https://pypi.python.org/account/register/";>register
You also need to be a maintainer (or an owner) of the <a
href="https://pypi.python.org/pypi/apache-beam";>apache-beam</a> package in
order to push a new release.
Ask on the mailing list for assistance.</p>
<h4 id="login-to-dockerhub">Login to DockerHub</h4>
-<p>Run following command manually.
+<p>If you are a member of the <a
href="https://hub.docker.com/orgs/apache/teams/beammaintainers";><code>beammaintainers</code>
DockerHub team</a>, run following command manually.
It will ask you to input your DockerHub ID and password if authorization info
cannot be found from ~/.docker/config.json file.</p>
<pre><code>docker login docker.io
</code></pre><p>After successful login, authorization info will be
stored at ~/.docker/config.json file.
@@ -910,7 +910,8 @@ For example,</p>
<pre><code>&quot;https://index.docker.io/v1/&quot;: {
&quot;auth&quot;: &quot;xxxxxx&quot;
}
-</code></pre><p>Release managers should have push permission; request
membership in the <a
href="https://hub.docker.com/orgs/apache/teams/beammaintainers";><code>beammaintainers</code>
team</a> by filing a JIRA with the Apache Infrastructure team, like <a
href="https://issues.apache.org/jira/browse/INFRA-20900";>INFRA-20900</a>.</p>
+</code></pre><p>If you are not already a member of the
<code>beammaintainers</code> team, please email <code>dev@</code>
for help with any DockerHub related tasks. We are not able
+to add more members to the DockerHub team because <a
href="https://infra.apache.org/docker-hub-policy.html";>the ASF has a limited
number of seats available</a>.</p>
<h3 id="create-a-new-milestone-in-github">Create a new milestone in
GitHub</h3>
<p>When contributors resolve an issue in GitHub, they are tagging it with a
release that will contain their changes.
With the release currently underway, new issues should be resolved against a
subsequent future release.
@@ -1236,7 +1237,9 @@ is perfectly safe since the script does not depend on the
current working tree.&
<li>Run gradle publish to push java artifacts into Maven staging
repo.</li>
<li>Stage source release into dist.apache.org dev <a
href="https://dist.apache.org/repos/dist/dev/beam/";>repo</a>.</li>
<li>Stage, sign and hash python source distribution and wheels into
dist.apache.org dev repo python dir</li>
-<li>Stage SDK docker images to <a
href="https://hub.docker.com/search?q=apache%2Fbeam&amp;type=image";>docker
hub Apache organization</a>.</li>
+<li>Stage SDK docker images to <a
href="https://hub.docker.com/search?q=apache%2Fbeam&amp;type=image";>docker
hub Apache organization</a>.
+Note: if you are not a member of the <a
href="https://hub.docker.com/orgs/apache/teams/beammaintainers";><code>beammaintainers</code>
DockerHub team</a> you will need
+help with this step. Please email <code>dev@</code> and ask a member of
the <code>beammaintainers</code> DockerHub team for help.</li>
<li>Create a PR to update beam-site, changes includes:
<ul>
<li>Copy python doc into beam-site</li>
@@ -1800,6 +1803,8 @@ All wheels should be published, in addition to the zip of
the release source.
(Signatures and hashes do <em>not</em> need to be uploaded.)</li>
</ul>
<h3 id="deploy-docker-images-to-dockerhub">Deploy docker images to
DockerHub</h3>
+<p>Note: if you are not a member of the <a
href="https://hub.docker.com/orgs/apache/teams/beammaintainers";>beammaintainers
DockerHub team</a>,
+you will need help with this step. Please email dev@ and ask a member of the
beammaintainers DockerHub team for help.</p>
<ul>
<li><strong>Script:</strong> <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/publish_docker_images.sh";>publish_docker_images.sh</a></li>
<li><strong>Usage</strong></li>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 0e7ebf852bd..fee1351c971 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -70,13 +70,14 @@ $ git checkout -b <my-branch> origin/release-docs
Background information about how the website is updated can be found in <a
href=https://s.apache.org/beam-site-automation>Beam-Site Automation
Reliability</a>.</p><h4 id=register-to-pypi>Register to PyPI</h4><p>Release
manager needs to have an account with PyPI.
If you need one, <a href=https://pypi.python.org/account/register/>register at
PyPI</a>.
You also need to be a maintainer (or an owner) of the <a
href=https://pypi.python.org/pypi/apache-beam>apache-beam</a> package in order
to push a new release.
-Ask on the mailing list for assistance.</p><h4 id=login-to-dockerhub>Login to
DockerHub</h4><p>Run following command manually.
+Ask on the mailing list for assistance.</p><h4 id=login-to-dockerhub>Login to
DockerHub</h4><p>If you are a member of the <a
href=https://hub.docker.com/orgs/apache/teams/beammaintainers><code>beammaintainers</code>
DockerHub team</a>, run following command manually.
It will ask you to input your DockerHub ID and password if authorization info
cannot be found from ~/.docker/config.json file.</p><pre><code>docker login
docker.io
</code></pre><p>After successful login, authorization info will be stored at
~/.docker/config.json file.
For example,</p><pre><code>"https://index.docker.io/v1/": {
"auth": "xxxxxx"
}
-</code></pre><p>Release managers should have push permission; request
membership in the <a
href=https://hub.docker.com/orgs/apache/teams/beammaintainers><code>beammaintainers</code>
team</a> by filing a JIRA with the Apache Infrastructure team, like <a
href=https://issues.apache.org/jira/browse/INFRA-20900>INFRA-20900</a>.</p><h3
id=create-a-new-milestone-in-github>Create a new milestone in
GitHub</h3><p>When contributors resolve an issue in GitHub, they are tagging it
with a release tha [...]
+</code></pre><p>If you are not already a member of the
<code>beammaintainers</code> team, please email <code>dev@</code> for help with
any DockerHub related tasks. We are not able
+to add more members to the DockerHub team because <a
href=https://infra.apache.org/docker-hub-policy.html>the ASF has a limited
number of seats available</a>.</p><h3
id=create-a-new-milestone-in-github>Create a new milestone in
GitHub</h3><p>When contributors resolve an issue in GitHub, they are tagging it
with a release that will contain their changes.
With the release currently underway, new issues should be resolved against a
subsequent future release.
Therefore, you should create a release item for this subsequent release, as
follows:</p><ol><li>In GitHub, navigate to <a
href=https://github.com/apache/beam/milestones><code>Issues > Milestones > New
Milestone</code></a>.</li><li>Add a new release. Choose the next minor version
number after the version currently underway, select the next release due date
(generally 6 weeks from today’s date) as the <code>Start Date</code>, and
choose <code>Create Milestone</code>.</li><li>At the end of [...]
related to the update have time to surface.</p><h2
id=4-investigate-performance-regressions>4. Investigate performance
regressions</h2><p>Check the Beam load tests for possible performance
regressions.
@@ -146,7 +147,9 @@ The final state of the repository should match this
diagram:</p><p><img src=/ima
adjust the version, and add the tag locally. If it looks good, run it again
with <code>--push-tag</code>.
If you already have a clone that includes the <code>${COMMIT_REF}</code> then
you can omit <code>--clone</code>. This
is perfectly safe since the script does not depend on the current working
tree.</p><p>See the source of the script for more details, or to run commands
manually in case of a problem.</p><h3
id=run-build_release_candidatesh-to-create-a-release-candidate>Run
build_release_candidate.sh to create a release
candidate</h3><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/build_release_candidate.sh>build_release_candidate.sh</a></p><
[...]
-</code></pre></li><li><p><strong>The script will:</strong></p><ol><li>Clone
the repo at the selected RC tag.</li><li>Run gradle publish to push java
artifacts into Maven staging repo.</li><li>Stage source release into
dist.apache.org dev <a
href=https://dist.apache.org/repos/dist/dev/beam/>repo</a>.</li><li>Stage, sign
and hash python source distribution and wheels into dist.apache.org dev repo
python dir</li><li>Stage SDK docker images to <a
href="https://hub.docker.com/search?q=apache% [...]
+</code></pre></li><li><p><strong>The script will:</strong></p><ol><li>Clone
the repo at the selected RC tag.</li><li>Run gradle publish to push java
artifacts into Maven staging repo.</li><li>Stage source release into
dist.apache.org dev <a
href=https://dist.apache.org/repos/dist/dev/beam/>repo</a>.</li><li>Stage, sign
and hash python source distribution and wheels into dist.apache.org dev repo
python dir</li><li>Stage SDK docker images to <a
href="https://hub.docker.com/search?q=apache% [...]
+Note: if you are not a member of the <a
href=https://hub.docker.com/orgs/apache/teams/beammaintainers><code>beammaintainers</code>
DockerHub team</a> you will need
+help with this step. Please email <code>dev@</code> and ask a member of the
<code>beammaintainers</code> DockerHub team for help.</li><li>Create a PR to
update beam-site, changes includes:<ul><li>Copy python doc into
beam-site</li><li>Copy java doc into beam-site</li></ul></li></ol></li></ul><h4
id=tasks-you-need-to-do-manually>Tasks you need to do
manually</h4><ol><li>Verify the script worked.<ol><li>Verify that the source
and Python binaries are present in <a href=https://dist.apache.o [...]
Please note that dependencies for the SDKs with different Python versions vary.
Need to verify all Python images by replacing <code>${ver}</code> with each
supported Python version <code>X.Y</code>.</li></ul><pre><code>docker run --rm
-it --entrypoint=/bin/bash
apache/beam_python${ver}_sdk:${RELEASE_VERSION}_rc{RC_NUM}
ls -al /opt/apache/beam/third_party_licenses/ | wc -l
@@ -415,7 +418,8 @@ Drop all other release candidates that are not being
released.</p><p><strong>NOT
please follow <a
href=https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/>the
guide</a> to configure command line access.</p><h3
id=deploy-python-artifacts-to-pypi>Deploy Python artifacts to
PyPI</h3><ul><li><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/deploy_pypi.sh>deploy_pypi.sh</a></li><li><strong>Usage</strong></li></ul><pre><code>./beam/release/src/main/scripts/deploy_pypi.sh
</code></pre><ul><li>Verify that the files at <a
href=https://pypi.org/project/apache-beam/#files>https://pypi.org/project/apache-beam/#files</a>
are correct.
All wheels should be published, in addition to the zip of the release source.
-(Signatures and hashes do <em>not</em> need to be uploaded.)</li></ul><h3
id=deploy-docker-images-to-dockerhub>Deploy docker images to
DockerHub</h3><ul><li><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/publish_docker_images.sh>publish_docker_images.sh</a></li><li><strong>Usage</strong></li></ul><pre><code>./beam/release/src/main/scripts/publish_docker_images.sh
+(Signatures and hashes do <em>not</em> need to be uploaded.)</li></ul><h3
id=deploy-docker-images-to-dockerhub>Deploy docker images to
DockerHub</h3><p>Note: if you are not a member of the <a
href=https://hub.docker.com/orgs/apache/teams/beammaintainers>beammaintainers
DockerHub team</a>,
+you will need help with this step. Please email dev@ and ask a member of the
beammaintainers DockerHub team for help.</p><ul><li><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/publish_docker_images.sh>publish_docker_images.sh</a></li><li><strong>Usage</strong></li></ul><pre><code>./beam/release/src/main/scripts/publish_docker_images.sh
</code></pre><ul><li><strong>Verify that:</strong><ul><li>Images are published
at <a
href="https://hub.docker.com/search?q=apache%2Fbeam&type=image";>DockerHub</a>
with tags {RELEASE_VERSION} and <em>latest</em>.</li><li>Images with
<em>latest</em> tag are pointing to current release by confirming the digest of
the image with <em>latest</em> tag is the same as the one with
{RELEASE_VERSION} tag.</li></ul></li></ul><p>(Optional) Clean up any unneeded
local images afterward to save disk spa [...]
gpg --output ~/doc.sig --sign ~/.bashrc
diff --git a/website/generated-content/documentation/index.xml
b/website/generated-content/documentation/index.xml
index 2c663f4b523..4b59192f9fa 100644
--- a/website/generated-content/documentation/index.xml
+++ b/website/generated-content/documentation/index.xml
@@ -5104,7 +5104,7 @@ programming guide, take a look at the
<li data-value="typescript">TypeScript SDK</li>
</ul>
</nav>
-<p class="language-py">The Python SDK supports Python 3.7, 3.8, 3.9, and
3.10.</p>
+<p class="language-py">The Python SDK supports Python 3.7, 3.8, 3.9, 3.10,
and 3.11.</p>
<p class="language-go">The Go SDK supports Go v1.19+. SDK release 2.32.0 is
the last experimental version.</p>
<p class="language-typescript">The Typescript SDK supports Node v16+ and is
still experimental.</p>
<h2 id="overview">1. Overview</h2>
@@ -6420,7 +6420,10 @@ an <code>init()</code> block.</p>
the execution of the ParDo transform. The comments give useful
information to pipeline developers such as the constraints that
apply to the objects or particular cases such as failover or
-instance reuse. They also give instantiation use cases.</p>
+instance reuse. They also give instantiation use cases. Two key points
+to note are that (1) teardown is done on a best effort basis and thus
+isn&rsquo;t guaranteed and (2) the number of DoFn instances is runner
+dependent.</p>
<!-- The source for the sequence diagram can be found in the SVG resource.
-->
<p><img src="/images/dofn-sequence-diagram.svg" alt="This is a sequence
diagram that shows the lifecycle of the DoFn"></p>
<h4 id="groupbykey">4.2.2. GroupByKey</h4>
diff --git
a/website/generated-content/documentation/programming-guide/index.html
b/website/generated-content/documentation/programming-guide/index.html
index 080ae96371e..70cad6b3de0 100644
--- a/website/generated-content/documentation/programming-guide/index.html
+++ b/website/generated-content/documentation/programming-guide/index.html
@@ -28,7 +28,7 @@ guide to programmatically building your Beam pipeline. As the
programming guide
is filled out, the text will include code samples in multiple languages to help
illustrate how to implement Beam concepts in your pipelines.</p><p>If you want
a brief introduction to Beam’s basic concepts before reading the
programming guide, take a look at the
-<a href=/documentation/basics/>Basics of the Beam model</a> page.</p><nav
class=language-switcher><strong>Adapt for:</strong><ul><li data-value=java
class=active>Java SDK</li><li data-value=py>Python SDK</li><li data-value=go>Go
SDK</li><li data-value=typescript>TypeScript SDK</li></ul></nav><p
class=language-py>The Python SDK supports Python 3.7, 3.8, 3.9, and 3.10.</p><p
class=language-go>The Go SDK supports Go v1.19+. SDK release 2.32.0 is the last
experimental version.</p><p class=la [...]
+<a href=/documentation/basics/>Basics of the Beam model</a> page.</p><nav
class=language-switcher><strong>Adapt for:</strong><ul><li data-value=java
class=active>Java SDK</li><li data-value=py>Python SDK</li><li data-value=go>Go
SDK</li><li data-value=typescript>TypeScript SDK</li></ul></nav><p
class=language-py>The Python SDK supports Python 3.7, 3.8, 3.9, 3.10, and
3.11.</p><p class=language-go>The Go SDK supports Go v1.19+. SDK release 2.32.0
is the last experimental version.</p><p cl [...]
of the Beam SDKs. Your driver program <em>defines</em> your pipeline,
including all of
the inputs, transforms, and outputs; it also sets execution options for your
pipeline (typically passed in using command-line options). These include the
@@ -716,7 +716,10 @@ an <code>init()</code> block.</p></blockquote></span><h5
id=dofn>4.2.1.4. DoFn l
the execution of the ParDo transform. The comments give useful
information to pipeline developers such as the constraints that
apply to the objects or particular cases such as failover or
-instance reuse. They also give instantiation use cases.</p><p><img
src=/images/dofn-sequence-diagram.svg alt="This is a sequence diagram that
shows the lifecycle of the DoFn"></p><h4 id=groupbykey>4.2.2.
GroupByKey</h4><p><code>GroupByKey</code> is a Beam transform for processing
collections of key/value pairs.
+instance reuse. They also give instantiation use cases. Two key points
+to note are that (1) teardown is done on a best effort basis and thus
+isn’t guaranteed and (2) the number of DoFn instances is runner
+dependent.</p><p><img src=/images/dofn-sequence-diagram.svg alt="This is a
sequence diagram that shows the lifecycle of the DoFn"></p><h4
id=groupbykey>4.2.2. GroupByKey</h4><p><code>GroupByKey</code> is a Beam
transform for processing collections of key/value pairs.
It’s a parallel reduction operation, analogous to the Shuffle phase of a
Map/Shuffle/Reduce-style algorithm. The input to <code>GroupByKey</code> is a
collection of
key/value pairs that represents a <em>multimap</em>, where the collection
contains
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 52249e72597..f2ce5171c0e 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-04-05T11:36:55-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-04-05T11:36:55-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-04-05T11:36:55-04:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-04-05T11:36:55-04: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-04-05T16:21:41-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-04-05T16:21:41-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-04-05T16:21:41-04:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-04-05T16:21:41-04:00</lastmod></url><url><loc>/catego
[...]
\ No newline at end of file
