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 2020/06/02 18:03:05 UTC

[beam] branch asf-site updated: Publishing website 2020/06/02 18:02:43 at commit 9c16b89

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 7b7a242  Publishing website 2020/06/02 18:02:43 at commit 9c16b89
7b7a242 is described below

commit 7b7a242e11665cf91d3c0368d57ce40d98fad9ce
Author: jenkins <bu...@apache.org>
AuthorDate: Tue Jun 2 18:02:44 2020 +0000

    Publishing website 2020/06/02 18:02:43 at commit 9c16b89
---
 website/generated-content/contribute/index.xml     | 35 ++++++++++++----------
 .../contribute/jira-priorities/index.html          | 14 +++++----
 .../documentation/runners/flink/index.html         |  2 +-
 .../roadmap/connectors-multi-sdk/index.html        |  2 +-
 website/generated-content/roadmap/index.xml        |  3 ++
 website/generated-content/sitemap.xml              |  2 +-
 6 files changed, 33 insertions(+), 25 deletions(-)

diff --git a/website/generated-content/contribute/index.xml b/website/generated-content/contribute/index.xml
index 96cfa6d..15cf853 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -1639,20 +1639,20 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 &lt;h1 id="jira-priorities">Jira Priorities&lt;/h1>
-&lt;h2 id="blocker--p0">Blocker / P0&lt;/h2>
-&lt;p>&lt;em>Expectation&lt;/em>: Drop everything else and work continuously to resolve. Note that
-the term &amp;ldquo;blocker&amp;rdquo; does not refer to blocking releases. A P0 issue is more
-urgent than simply blocking the next release.&lt;/p>
-&lt;p>&lt;em>Example Blocker/P0 issues&lt;/em>:&lt;/p>
+&lt;h2 id="p0-outage">P0: Outage&lt;/h2>
+&lt;p>&lt;em>Expectation&lt;/em>: Drop everything else and work continuously to resolve. An outage
+means that some piece of infrastructure that the community relies on is down. A
+P0 issue is &lt;em>more&lt;/em> urgent than simply blocking the next release.&lt;/p>
+&lt;p>&lt;em>Example P0 issues&lt;/em>:&lt;/p>
 &lt;ul>
 &lt;li>the build is broken, halting all development&lt;/li>
 &lt;li>the website is down&lt;/li>
 &lt;li>a vulnerability requires a point release ASAP&lt;/li>
 &lt;/ul>
-&lt;h2 id="critical--p1">Critical / P1&lt;/h2>
-&lt;p>&lt;em>Expectation&lt;/em>: Continuous status updates. Critical bugs should not be
-unassigned. Most critical bugs should block release.&lt;/p>
-&lt;p>&lt;em>Example Critical/P1 issues&lt;/em>:&lt;/p>
+&lt;h2 id="p1-critical">P1: Critical&lt;/h2>
+&lt;p>&lt;em>Expectation&lt;/em>: Continuous status updates. P1 bugs should not be
+unassigned. Most P1 bugs should block release.&lt;/p>
+&lt;p>&lt;em>Example P1 issues&lt;/em>:&lt;/p>
 &lt;ul>
 &lt;li>data loss error&lt;/li>
 &lt;li>important component is nonfunctional for important use cases&lt;/li>
@@ -1660,26 +1660,29 @@ unassigned. Most critical bugs should block release.&lt;/p>
 &lt;li>failing postcommit test&lt;/li>
 &lt;li>flaky test&lt;/li>
 &lt;/ul>
-&lt;h2 id="major--p2">Major / P2&lt;/h2>
+&lt;h2 id="p2-default">P2: Default&lt;/h2>
 &lt;p>&lt;em>Expectation&lt;/em>: Most tickets fall into this priority. These can be planned and
-executed by anyone who is interested. No special urgency is associated.&lt;/p>
-&lt;p>&lt;em>Example Major/P2 issues&lt;/em>&lt;/p>
+executed by anyone who is interested. No special urgency is associated, but if
+no action is taken on a P2 ticket for a long time, it indicates it is actually
+just P3/nice-to-have.&lt;/p>
+&lt;p>&lt;em>Example P2 issues&lt;/em>&lt;/p>
 &lt;ul>
 &lt;li>typical feature request&lt;/li>
 &lt;li>bug that affects some use cases but don&amp;rsquo;t make a component nonfunctional&lt;/li>
 &lt;li>ignored (&amp;ldquo;sickbayed&amp;rdquo;) test&lt;/li>
 &lt;/ul>
-&lt;h2 id="minor--p3">Minor / P3&lt;/h2>
+&lt;h2 id="p3-nice-to-have">P3: Nice-to-have&lt;/h2>
 &lt;p>&lt;em>Expectation&lt;/em>: Nice-to-have improvements.&lt;/p>
-&lt;p>&lt;em>Example Minor/P3 issues&lt;/em>&lt;/p>
+&lt;p>&lt;em>Example P3 issues&lt;/em>&lt;/p>
 &lt;ul>
 &lt;li>feature request that is nice-to-have&lt;/li>
+&lt;li>ticket filed as P2 that no one finds time to work on&lt;/li>
 &lt;/ul>
-&lt;h2 id="trivial--p4">Trivial / P4&lt;/h2>
+&lt;h2 id="p4">P4&lt;/h2>
 &lt;p>&lt;em>Expectation&lt;/em>: Nice-to-have improvements that are also very small and easy.
 Usually it is quicker to just fix them than to file a bug, but the Jira
 can be referenced by a pull request and shows up in release notes.&lt;/p>
-&lt;p>&lt;em>Example Trivial/P4 issues&lt;/em>&lt;/p>
+&lt;p>&lt;em>Example P4 issues&lt;/em>&lt;/p>
 &lt;ul>
 &lt;li>spelling errors in comments or code&lt;/li>
 &lt;/ul></description></item><item><title>Contribute: Post-commit policies details</title><link>/contribute/postcommits-policies-details/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/contribute/postcommits-policies-details/</guid><description>
diff --git a/website/generated-content/contribute/jira-priorities/index.html b/website/generated-content/contribute/jira-priorities/index.html
index 4b95113..66564e6 100644
--- a/website/generated-content/contribute/jira-priorities/index.html
+++ b/website/generated-content/contribute/jira-priorities/index.html
@@ -1,13 +1,15 @@
 <!doctype html><html lang=en class=no-js><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge"><meta name=viewport content="width=device-width,initial-scale=1"><title>Jira Priorities</title><meta name=description content="Apache Beam is an open source, unified model and set of language-specific SDKs for defining and executing data processing workflows, and also data ingestion and integration flows, supporting Enterprise Integration Patterns (EIPs) and Domain Specif [...]
 <span class=sr-only>Toggle navigation</span>
 <span class=icon-bar></span><span class=icon-bar></span><span class=icon-bar></span></button>
-<a href=/ class=navbar-brand><img alt=Brand style=height:25px src=/images/beam_logo_navbar.png></a></div><div class="navbar-mask closed"></div><div id=navbar class="navbar-container closed"><ul class="nav navbar-nav"><li><a href=/get-started/beam-overview/>Get Started</a></li><li><a href=/documentation/>Documentation</a></li><li><a href=/documentation/sdks/java/>Languages</a></li><li><a href=/documentation/runners/capability-matrix/>RUNNERS</a></li><li><a href=/roadmap/>Roadmap</a></li>< [...]
-the term &ldquo;blocker&rdquo; does not refer to blocking releases. A P0 issue is more
-urgent than simply blocking the next release.</p><p><em>Example Blocker/P0 issues</em>:</p><ul><li>the build is broken, halting all development</li><li>the website is down</li><li>a vulnerability requires a point release ASAP</li></ul><h2 id=critical--p1>Critical / P1</h2><p><em>Expectation</em>: Continuous status updates. Critical bugs should not be
-unassigned. Most critical bugs should block release.</p><p><em>Example Critical/P1 issues</em>:</p><ul><li>data loss error</li><li>important component is nonfunctional for important use cases</li><li>major performance regression</li><li>failing postcommit test</li><li>flaky test</li></ul><h2 id=major--p2>Major / P2</h2><p><em>Expectation</em>: Most tickets fall into this priority. These can be planned and
-executed by anyone who is interested. No special urgency is associated.</p><p><em>Example Major/P2 issues</em></p><ul><li>typical feature request</li><li>bug that affects some use cases but don&rsquo;t make a component nonfunctional</li><li>ignored (&ldquo;sickbayed&rdquo;) test</li></ul><h2 id=minor--p3>Minor / P3</h2><p><em>Expectation</em>: Nice-to-have improvements.</p><p><em>Example Minor/P3 issues</em></p><ul><li>feature request that is nice-to-have</li></ul><h2 id=trivial--p4>Triv [...]
+<a href=/ class=navbar-brand><img alt=Brand style=height:25px src=/images/beam_logo_navbar.png></a></div><div class="navbar-mask closed"></div><div id=navbar class="navbar-container closed"><ul class="nav navbar-nav"><li><a href=/get-started/beam-overview/>Get Started</a></li><li><a href=/documentation/>Documentation</a></li><li><a href=/documentation/sdks/java/>Languages</a></li><li><a href=/documentation/runners/capability-matrix/>RUNNERS</a></li><li><a href=/roadmap/>Roadmap</a></li>< [...]
+means that some piece of infrastructure that the community relies on is down. A
+P0 issue is <em>more</em> urgent than simply blocking the next release.</p><p><em>Example P0 issues</em>:</p><ul><li>the build is broken, halting all development</li><li>the website is down</li><li>a vulnerability requires a point release ASAP</li></ul><h2 id=p1-critical>P1: Critical</h2><p><em>Expectation</em>: Continuous status updates. P1 bugs should not be
+unassigned. Most P1 bugs should block release.</p><p><em>Example P1 issues</em>:</p><ul><li>data loss error</li><li>important component is nonfunctional for important use cases</li><li>major performance regression</li><li>failing postcommit test</li><li>flaky test</li></ul><h2 id=p2-default>P2: Default</h2><p><em>Expectation</em>: Most tickets fall into this priority. These can be planned and
+executed by anyone who is interested. No special urgency is associated, but if
+no action is taken on a P2 ticket for a long time, it indicates it is actually
+just P3/nice-to-have.</p><p><em>Example P2 issues</em></p><ul><li>typical feature request</li><li>bug that affects some use cases but don&rsquo;t make a component nonfunctional</li><li>ignored (&ldquo;sickbayed&rdquo;) test</li></ul><h2 id=p3-nice-to-have>P3: Nice-to-have</h2><p><em>Expectation</em>: Nice-to-have improvements.</p><p><em>Example P3 issues</em></p><ul><li>feature request that is nice-to-have</li><li>ticket filed as P2 that no one finds time to work on</li></ul><h2 id=p4>P4 [...]
 Usually it is quicker to just fix them than to file a bug, but the Jira
-can be referenced by a pull request and shows up in release notes.</p><p><em>Example Trivial/P4 issues</em></p><ul><li>spelling errors in comments or code</li></ul></div></div><footer class=footer><div class=footer__contained><div class=footer__cols><div class=footer__cols__col><div class=footer__cols__col__logo><img src=/images/beam_logo_circle.svg class=footer__logo alt="Beam logo"></div><div class=footer__cols__col__logo><img src=/images/apache_logo_circle.svg class=footer__logo alt=" [...]
+can be referenced by a pull request and shows up in release notes.</p><p><em>Example P4 issues</em></p><ul><li>spelling errors in comments or code</li></ul></div></div><footer class=footer><div class=footer__contained><div class=footer__cols><div class=footer__cols__col><div class=footer__cols__col__logo><img src=/images/beam_logo_circle.svg class=footer__logo alt="Beam logo"></div><div class=footer__cols__col__logo><img src=/images/apache_logo_circle.svg class=footer__logo alt="Apache l [...]
 <a href=http://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></footer></body></html>
\ No newline at end of file
diff --git a/website/generated-content/documentation/runners/flink/index.html b/website/generated-content/documentation/runners/flink/index.html
index ae427aa..9016464 100644
--- a/website/generated-content/documentation/runners/flink/index.html
+++ b/website/generated-content/documentation/runners/flink/index.html
@@ -78,7 +78,7 @@ plus the optional <code>flink_version</code> and <code>flink_master</code> optio
     <span class=o>...</span></code></pre></div></div><h2 id=additional-information-and-caveats>Additional information and caveats</h2><h3 id=monitoring-your-job>Monitoring your job</h3><p>You can monitor a running Flink job using the Flink JobManager Dashboard or its Rest interfaces. By default, this is available at port <code>8081</code> of the JobManager node. If you have a Flink installation on your local machine that would be <code>http://localhost:8081</code>. Note: When you use the [...]
 Many sources like <code>PubSubIO</code> rely on their checkpoints to be acknowledged which can only be done when checkpointing is enabled for the <code>FlinkRunner</code>. To enable checkpointing, please set <span class=language-java><code>checkpointingInterval</code></span><span class=language-py><code>checkpointing_interval</code></span> to the desired checkpointing interval in milliseconds.</p><h2 id=pipeline-options-for-the-flink-runner>Pipeline options for the Flink Runner</h2><p>Wh [...]
 <a href=https://beam.apache.org/releases/javadoc/2.21.0/index.html?org/apache/beam/runners/flink/FlinkPipelineOptions.html>FlinkPipelineOptions</a>
-reference class:</p><div class=language-java><table class="table table-bordered"><tr><td><code>allowNonRestoredState</code></td><td>Flag indicating whether non restored state is allowed if the savepoint contains state for an operator that is no longer part of the pipeline.</td><td>Default: <code>false</code></td></tr><tr><td><code>autoBalanceWriteFilesShardingEnabled</code></td><td>Flag indicating whether auto-balance sharding for WriteFiles transform should be enabled. This might prove  [...]
+reference class:</p><div class=language-java><table class="table table-bordered"><tr><td><code>allowNonRestoredState</code></td><td>Flag indicating whether non restored state is allowed if the savepoint contains state for an operator that is no longer part of the pipeline.</td><td>Default: <code>false</code></td></tr><tr><td><code>autoBalanceWriteFilesShardingEnabled</code></td><td>Flag indicating whether auto-balance sharding for WriteFiles transform should be enabled. This might prove  [...]
 <a href=https://beam.apache.org/releases/javadoc/2.21.0/index.html?org/apache/beam/sdk/options/PipelineOptions.html>PipelineOptions</a>
 reference.</p><h2 id=capability>Capability</h2><p>The <a href=/documentation/runners/capability-matrix/>Beam Capability Matrix</a> documents the
 capabilities of the classic Flink Runner.</p><p>The <a href=https://s.apache.org/apache-beam-portability-support-table>Portable Capability
diff --git a/website/generated-content/roadmap/connectors-multi-sdk/index.html b/website/generated-content/roadmap/connectors-multi-sdk/index.html
index 5d686b1..e60d8c5 100644
--- a/website/generated-content/roadmap/connectors-multi-sdk/index.html
+++ b/website/generated-content/roadmap/connectors-multi-sdk/index.html
@@ -5,7 +5,7 @@
 replace current frameworks for developing bounded and unbounded sources.
 Splittable DoFn is being developed along side current Beam portability
 efforts. See <a href=https://beam.apache.org/roadmap/portability/>Beam portability framework roadmap</a> for more details.</p><h1 id=cross-language-transforms>Cross-language transforms</h1><p><em>Last updated on May 2020.</em></p><p>As an added benefit of Beam portability effort, we are able to utilize Beam transforms across SDKs. This has many benefits.</p><ul><li>Connector sharing across SDKs. For example,<ul><li>Beam pipelines written using Python and Go SDKs will be able to utilize t [...]
-language of choice and utilize these transforms from other languages reducing the maintenance and support overheads.</li><li><a href=https://beam.apache.org/documentation/dsls/sql/overview/>Beam SQL</a>, that is currently only available to Java SDK, will become available to Python and Go SDKs.</li><li><a href=https://www.tensorflow.org/tfx/transform/get_started>Beam TFX transforms</a>, that are currently only available to Beam Python SDK pipelines will become available to Java and Go SDK [...]
+language of choice and utilize these transforms from other languages reducing the maintenance and support overheads.</li><li><a href=https://beam.apache.org/documentation/dsls/sql/overview/>Beam SQL</a>, that is currently only available to Java SDK, will become available to Python and Go SDKs.</li><li><a href=https://www.tensorflow.org/tfx/transform/get_started>Beam TFX transforms</a>, that are currently only available to Beam Python SDK pipelines will become available to Java and Go SDK [...]
 <a href=http://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></footer></body></html>
\ No newline at end of file
diff --git a/website/generated-content/roadmap/index.xml b/website/generated-content/roadmap/index.xml
index dc4c083..aeb275b 100644
--- a/website/generated-content/roadmap/index.xml
+++ b/website/generated-content/roadmap/index.xml
@@ -301,8 +301,11 @@ language of choice and utilize these transforms from other languages reducing th
 &lt;h3 id="connectortransform-support">Connector/transform support&lt;/h3>
 &lt;p>Ongoing and planned work related to making existing connectors/transforms available to other SDKs through the cross-language transforms framework.&lt;/p>
 &lt;ul>
+&lt;li>Java JdbcIO - In progress - &lt;a href="https://issues.apache.org/jira/browse/BEAM-10135">BEAM-10135&lt;/a>, &lt;a href="https://issues.apache.org/jira/browse/BEAM-10136">BEAM-10136&lt;/a>&lt;/li>
 &lt;li>Java KafkaIO - completed - &lt;a href="https://issues.apache.org/jira/browse/BEAM-7029">BEAM-7029&lt;/a>&lt;/li>
+&lt;li>Java KinesisIO - In progress - &lt;a href="https://issues.apache.org/jira/browse/BEAM-10137">BEAM-10137&lt;/a>, &lt;a href="https://issues.apache.org/jira/browse/BEAM-10138">BEAM-10138&lt;/a>&lt;/li>
 &lt;li>Java PubSubIO - In progress - &lt;a href="https://issues.apache.org/jira/browse/BEAM-7738">BEAM-7738&lt;/a>&lt;/li>
+&lt;li>Java SpannerIO - In progress - &lt;a href="https://issues.apache.org/jira/browse/BEAM-10139">BEAM-10139&lt;/a>, &lt;a href="https://issues.apache.org/jira/browse/BEAM-10140">BEAM-10140&lt;/a>&lt;/li>
 &lt;li>Java SQL - completed - &lt;a href="https://issues.apache.org/jira/browse/BEAM-8603">BEAM-8603&lt;/a>&lt;/li>
 &lt;/ul>
 &lt;h3 id="portable-beam-schema">Portable Beam schema&lt;/h3>
diff --git a/website/generated-content/sitemap.xml b/website/generated-content/sitemap.xml
index d544949..312a332 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>/categories/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/python/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/ [...]
\ 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>/categories/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/python/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/ [...]
\ No newline at end of file