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 b27a42b Publishing website 2020/10/28 00:02:59 at commit f44abcd
b27a42b is described below
commit b27a42b53a21af8d39a5e24bf78e95f247e85157
Author: jenkins <bui...@apache.org>
AuthorDate: Wed Oct 28 00:02:59 2020 +0000
Publishing website 2020/10/28 00:02:59 at commit f44abcd
---
website/generated-content/contribute/index.xml | 12 ++---------
.../contribute/release-guide/index.html | 13 +-----------
website/generated-content/documentation/index.xml | 23 ++++++++++++++--------
.../documentation/programming-guide/index.html | 17 +++++++++-------
website/generated-content/sitemap.xml | 2 +-
5 files changed, 29 insertions(+), 38 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index a92c799..e2e0828 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -498,16 +498,8 @@ authorization info cannot be found from
~/.docker/config.json file.</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; please
ask for help at dev@.</p>
-<pre><code>From: Release Manager
-To: d...@beam.apache.org
-Subject: DockerHub Push Permission
-Hi DockerHub Admins
-I need push permission to proceed with release, can you please add me to
maintainer team?
-My docker hub ID is: xxx
-Thanks,
-Release Manager
-</code></pre><h3 id="create-a-new-version-in-jira">Create a new
version in JIRA</h3>
+</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-version-in-jira">Create a new version in JIRA</h3>
<p>When contributors resolve an issue in JIRA, 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>
<p><strong>Attention</strong>: Only PMC has permission to perform
this. If you are not a PMC, please ask for help in dev@ mailing list.</p>
<ol>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 6b973f3..44e6758 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -43,18 +43,7 @@ authorization info cannot be found from
~/.docker/config.json file.</p><pre><cod
</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; please ask for
help at dev@.</p><pre><code>From: Release Manager
-To: d...@beam.apache.org
-Subject: DockerHub Push Permission
-
-Hi DockerHub Admins
-
-I need push permission to proceed with release, can you please add me to
maintainer team?
-My docker hub ID is: xxx
-
-Thanks,
-Release Manager
-</code></pre><h3 id=create-a-new-version-in-jira>Create a new version in
JIRA</h3><p>When contributors resolve an issue in JIRA, 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><p><strong>Attention</strong>: Only PMC has permission to perform
this. If you are not a PMC, please as [...]
+</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-version-in-jira>Create a new version in JIRA</h3><p>When
contributors resolve an issue in JIRA, they are tagging it with a release that
will con [...]
The role of the release manager is to file JIRA issues for each regression
with the ‘Fix Version’ set to the to-be-released version. The
release manager
oversees these just like any other JIRA issue marked with the ‘Fix
Version’ of the release.</p><p>The mailing list should be informed to
allow fixing the regressions in the course of the release.</p><h2
id=4-create-a-release-branch-in-apachebeam-repository>4. Create a release
branch in apache/beam repository</h2><p>Attention: Only committer has
permission to create release branch in apache/beam.</p><p>Release candidates
are built from a release branch. As a final step in prep [...]
./beam/release/src/main/scripts/cut_release_branch.sh \
diff --git a/website/generated-content/documentation/index.xml
b/website/generated-content/documentation/index.xml
index 1e69071..c1e1c04 100644
--- a/website/generated-content/documentation/index.xml
+++ b/website/generated-content/documentation/index.xml
@@ -4934,23 +4934,30 @@ schema for PCollections with
<code>NamedTuple</code> output types. For exa
<span class="n">purchase_amount</span><span class="p">:</span>
<span class="nb">float</span>
<span class="n">pc</span> <span class="o">=</span> <span
class="nb">input</span> <span class="o">|</span> <span
class="n">beam</span><span class="o">.</span><span
class="n">Map</span><span class="p">(</span><span
class="k">lambda</span> <span class="o">...</span><span
class="p">)</span><span class="o">.</span><span
class="n">with_output_types</span><span class="p">(</span><span
class="n">Transaction< [...]
</div>
-<p class="language-py"><strong>beam.Row</strong></p>
-<p class="language-py">It&rsquo;s also possible to create ad-hoc schema
declarations with a simple lambda
-that returns instances of <code>beam.Row</code>:</p>
+<p class="language-py"><strong>beam.Row and Select</strong></p>
+<p class="language-py">There are also methods for creating ad-hoc schema
declarations. First, you can
+use a lambda that returns instances of <code>beam.Row</code>:</p>
<div class=language-py>
<div class="highlight"><pre class="chroma"><code class="language-py"
data-lang="py"><span class="n">input_pc</span> <span
class="o">=</span> <span class="o">...</span> <span class="c1">#
{&#34;bank&#34;: ..., &#34;purchase_amount&#34;: ...}</span>
<span class="n">output_pc</span> <span class="o">=</span> <span
class="n">input_pc</span> <span class="o">|</span> <span
class="n">beam</span><span class="o">.</span><span
class="n">Map</span><span class="p">(</span><span
class="k">lambda</span> <span class="n">item</span><span
class="p">:</span> <span class="n">beam</span><span
class="o">.</span><span class="n">Row</span><span
class="p">(</span>< [...]
<span class="n">purchase_amount</span><span
class="o">=</span><span class="n">item</span><span
class="p">[</span><span
class="s2">&#34;purchase_amount&#34;</span><span
class="p">])</span></code></pre></div>
</div>
-<p class="language-py">Note that this declaration doesn&rsquo;t include
any specific information about the
-types of the <code>bank</code> and <code>purchase_amount</code>
fields. Beam will attempt to infer
-type information, if it&rsquo;s unable to it will fall back to the generic
type
+<p class="language-py">Sometimes it can be more concise to express the same
logic with the
+<a
href="https://beam.apache.org/releases/pydoc/current/apache_beam.transforms.core.html#apache_beam.transforms.core.Select";><code>Select</code></a>
transform:</p>
+<div class=language-py>
+<div class="highlight"><pre class="chroma"><code class="language-py"
data-lang="py"><span class="n">input_pc</span> <span
class="o">=</span> <span class="o">...</span> <span class="c1">#
{&#34;bank&#34;: ..., &#34;purchase_amount&#34;: ...}</span>
+<span class="n">output_pc</span> <span class="o">=</span> <span
class="n">input_pc</span> <span class="o">|</span> <span
class="n">beam</span><span class="o">.</span><span
class="n">Select</span><span class="p">(</span><span
class="n">bank</span><span class="o">=</span><span
class="k">lambda</span> <span class="n">item</span><span
class="p">:</span> <span class="n">item</span><span
class="p">[</span [...]
+<span class="n">purchase_amount</span><span
class="o">=</span><span class="k">lambda</span> <span
class="n">item</span><span class="p">:</span> <span
class="n">item</span><span class="p">[</span><span
class="s2">&#34;purchase_amount&#34;</span><span
class="p">])</span></code></pre></div>
+</div>
+<p class="language-py">Note that these declaration don&rsquo;t include
any specific information about the
+types of the <code>bank</code> and <code>purchase_amount</code>
fields, so Beam will attempt to infer
+type information. If it&rsquo;s unable to it will fall back to the generic
type
<code>Any</code>. Sometimes this is not ideal, you can use casts to make
sure Beam
-correctly infers types with <code>beam.Row</code>:</p>
+correctly infers types with <code>beam.Row</code> or with
<code>Select</code>:</p>
<div class=language-py>
<div class="highlight"><pre class="chroma"><code class="language-py"
data-lang="py"><span class="n">input_pc</span> <span
class="o">=</span> <span class="o">...</span> <span class="c1">#
{&#34;bank&#34;: ..., &#34;purchase_amount&#34;: ...}</span>
<span class="n">output_pc</span> <span class="o">=</span> <span
class="n">input_pc</span> <span class="o">|</span> <span
class="n">beam</span><span class="o">.</span><span
class="n">Map</span><span class="p">(</span><span
class="k">lambda</span> <span class="n">item</span><span
class="p">:</span> <span class="n">beam</span><span
class="o">.</span><span class="n">Row</span><span
class="p">(</span>< [...]
-<span class="n">purchase_amount</span><span
class="o">=</span><span class="nb">float</span><span
class="p">(</span><span class="n">item</span><span
class="p">[</span><span
class="s2">&#34;purchase_amount&#34;</span><span
class="p">]))</span></code></pre></div>
+<span class="n">purchase_amount</span><span
class="o">=</span><span class="nb">float</span><span
class="p">(</span><span class="n">item</span><span
class="p">[</span><span
class="s2">&#34;purchase_amount&#34;</span><span
class="p">])))</span></code></pre></div>
</div>
<h3 id="using-schemas">6.6. Using Schema Transforms</h3>
<p>A schema on a <code>PCollection</code> enables a rich variety of
relational transforms. The fact that each record is composed of
diff --git
a/website/generated-content/documentation/programming-guide/index.html
b/website/generated-content/documentation/programming-guide/index.html
index 8de8bae..6595d9e 100644
--- a/website/generated-content/documentation/programming-guide/index.html
+++ b/website/generated-content/documentation/programming-guide/index.html
@@ -1565,16 +1565,19 @@ schema for PCollections with <code>NamedTuple</code>
output types. For example:<
<span class=n>bank</span><span class=p>:</span> <span class=nb>str</span>
<span class=n>purchase_amount</span><span class=p>:</span> <span
class=nb>float</span>
-<span class=n>pc</span> <span class=o>=</span> <span class=nb>input</span>
<span class=o>|</span> <span class=n>beam</span><span class=o>.</span><span
class=n>Map</span><span class=p>(</span><span class=k>lambda</span> <span
class=o>...</span><span class=p>)</span><span class=o>.</span><span
class=n>with_output_types</span><span class=p>(</span><span
class=n>Transaction</span><span class=p>)</span></code></pre></div></div><p
class=language-py><strong>beam.Row</strong></p><p class=languag [...]
-that returns instances of <code>beam.Row</code>:</p><div
class=language-py><div class=highlight><pre class=chroma><code
class=language-py data-lang=py><span class=n>input_pc</span> <span
class=o>=</span> <span class=o>...</span> <span class=c1># {"bank":
..., "purchase_amount": ...}</span>
+<span class=n>pc</span> <span class=o>=</span> <span class=nb>input</span>
<span class=o>|</span> <span class=n>beam</span><span class=o>.</span><span
class=n>Map</span><span class=p>(</span><span class=k>lambda</span> <span
class=o>...</span><span class=p>)</span><span class=o>.</span><span
class=n>with_output_types</span><span class=p>(</span><span
class=n>Transaction</span><span class=p>)</span></code></pre></div></div><p
class=language-py><strong>beam.Row and Select</strong></p><p cl [...]
+use a lambda that returns instances of <code>beam.Row</code>:</p><div
class=language-py><div class=highlight><pre class=chroma><code
class=language-py data-lang=py><span class=n>input_pc</span> <span
class=o>=</span> <span class=o>...</span> <span class=c1># {"bank":
..., "purchase_amount": ...}</span>
<span class=n>output_pc</span> <span class=o>=</span> <span
class=n>input_pc</span> <span class=o>|</span> <span class=n>beam</span><span
class=o>.</span><span class=n>Map</span><span class=p>(</span><span
class=k>lambda</span> <span class=n>item</span><span class=p>:</span> <span
class=n>beam</span><span class=o>.</span><span class=n>Row</span><span
class=p>(</span><span class=n>bank</span><span class=o>=</span><span
class=n>item</span><span class=p>[</span><span class=s2>"bank" [...]
- <span
class=n>purchase_amount</span><span class=o>=</span><span
class=n>item</span><span class=p>[</span><span
class=s2>"purchase_amount"</span><span
class=p>])</span></code></pre></div></div><p class=language-py>Note that this
declaration doesn’t include any specific information about the
-types of the <code>bank</code> and <code>purchase_amount</code> fields. Beam
will attempt to infer
-type information, if it’s unable to it will fall back to the generic type
+ <span
class=n>purchase_amount</span><span class=o>=</span><span
class=n>item</span><span class=p>[</span><span
class=s2>"purchase_amount"</span><span
class=p>])</span></code></pre></div></div><p class=language-py>Sometimes it can
be more concise to express the same logic with the
+<a
href=https://beam.apache.org/releases/pydoc/current/apache_beam.transforms.core.html#apache_beam.transforms.core.Select><code>Select</code></a>
transform:</p><div class=language-py><div class=highlight><pre
class=chroma><code class=language-py data-lang=py><span class=n>input_pc</span>
<span class=o>=</span> <span class=o>...</span> <span class=c1>#
{"bank": ..., "purchase_amount": ...}</span>
+<span class=n>output_pc</span> <span class=o>=</span> <span
class=n>input_pc</span> <span class=o>|</span> <span class=n>beam</span><span
class=o>.</span><span class=n>Select</span><span class=p>(</span><span
class=n>bank</span><span class=o>=</span><span class=k>lambda</span> <span
class=n>item</span><span class=p>:</span> <span class=n>item</span><span
class=p>[</span><span class=s2>"bank"</span><span class=p>],</span>
+ <span class=n>purchase_amount</span><span
class=o>=</span><span class=k>lambda</span> <span class=n>item</span><span
class=p>:</span> <span class=n>item</span><span class=p>[</span><span
class=s2>"purchase_amount"</span><span
class=p>])</span></code></pre></div></div><p class=language-py>Note that these
declaration don’t include any specific information about the
+types of the <code>bank</code> and <code>purchase_amount</code> fields, so
Beam will attempt to infer
+type information. If it’s unable to it will fall back to the generic type
<code>Any</code>. Sometimes this is not ideal, you can use casts to make sure
Beam
-correctly infers types with <code>beam.Row</code>:</p><div
class=language-py><div class=highlight><pre class=chroma><code
class=language-py data-lang=py><span class=n>input_pc</span> <span
class=o>=</span> <span class=o>...</span> <span class=c1># {"bank":
..., "purchase_amount": ...}</span>
+correctly infers types with <code>beam.Row</code> or with
<code>Select</code>:</p><div class=language-py><div class=highlight><pre
class=chroma><code class=language-py data-lang=py><span class=n>input_pc</span>
<span class=o>=</span> <span class=o>...</span> <span class=c1>#
{"bank": ..., "purchase_amount": ...}</span>
<span class=n>output_pc</span> <span class=o>=</span> <span
class=n>input_pc</span> <span class=o>|</span> <span class=n>beam</span><span
class=o>.</span><span class=n>Map</span><span class=p>(</span><span
class=k>lambda</span> <span class=n>item</span><span class=p>:</span> <span
class=n>beam</span><span class=o>.</span><span class=n>Row</span><span
class=p>(</span><span class=n>bank</span><span class=o>=</span><span
class=nb>str</span><span class=p>(</span><span class=n>item</span><spa [...]
- <span
class=n>purchase_amount</span><span class=o>=</span><span
class=nb>float</span><span class=p>(</span><span class=n>item</span><span
class=p>[</span><span class=s2>"purchase_amount"</span><span
class=p>]))</span></code></pre></div></div><h3 id=using-schemas>6.6. Using
Schema Transforms</h3><p>A schema on a <code>PCollection</code> enables a rich
variety of relational transforms. The fact that each record is composed of
+ <span
class=n>purchase_amount</span><span class=o>=</span><span
class=nb>float</span><span class=p>(</span><span class=n>item</span><span
class=p>[</span><span class=s2>"purchase_amount"</span><span
class=p>])))</span></code></pre></div></div><h3 id=using-schemas>6.6. Using
Schema Transforms</h3><p>A schema on a <code>PCollection</code> enables a rich
variety of relational transforms. The fact that each record is composed of
named fields allows for simple and readable aggregations that reference fields
by name, similar to the aggregations in
a SQL expression.</p><h4 id=661-field-selection-syntax>6.6.1. Field selection
syntax</h4><p>The advantage of schemas is that they allow referencing of
element fields by name. Beam provides a selection syntax for
referencing fields, including nested and repeated fields. This syntax is used
by all of the schema transforms when
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 87706e6..5e1f1df 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.25.0/</loc><lastmod>2020-10-26T10:46:37-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2020-10-26T10:46:37-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-10-26T10:46:37-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-10-26T10:46:37-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.25.0/</loc><lastmod>2020-10-26T10:46:37-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2020-10-26T10:46:37-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-10-26T10:46:37-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-10-26T10:46:37-07:00</lastmod></url><url><loc>/blog/b
[...]
\ No newline at end of file
