This is an automated email from the ASF dual-hosted git repository.
bbejeck pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new ac68854 MINOR: Update stream documentation for version 2.5 (#265)
ac68854 is described below
commit ac68854e9bde605d15e39849893095027b3ff108
Author: showuon <43372967+show...@users.noreply.github.com>
AuthorDate: Tue May 19 23:21:00 2020 +0800
MINOR: Update stream documentation for version 2.5 (#265)
1. fix broken links
2. rephrase a sentence
3. update the version number
Reviewers: Bill Bejeck <bbej...@apache.org>
---
25/streams/architecture.html | 2 +-
25/streams/developer-guide/dsl-api.html | 2 +-
25/streams/developer-guide/running-app.html | 2 +-
25/streams/developer-guide/write-streams.html | 4 ++--
25/streams/upgrade-guide.html | 6 +++---
5 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/25/streams/architecture.html b/25/streams/architecture.html
index 7efd7ea..711f883 100644
--- a/25/streams/architecture.html
+++ b/25/streams/architecture.html
@@ -111,7 +111,7 @@
<p>
Kafka Streams provides so-called <b>state stores</b>, which can be
used by stream processing applications to store and query data,
- which is an important capability when implementing stateful
operations. The <a
href="/{{version}}/documentation/streams/developer-guide#streams_dsl">Kafka
Streams DSL</a>, for example, automatically creates
+ which is an important capability when implementing stateful
operations. The <a
href="/{{version}}/documentation/streams/developer-guide/dsl-api.html">Kafka
Streams DSL</a>, for example, automatically creates
and manages such state stores when you are calling stateful operators
such as <code>join()</code> or <code>aggregate()</code>, or when you are
windowing a stream.
</p>
diff --git a/25/streams/developer-guide/dsl-api.html
b/25/streams/developer-guide/dsl-api.html
index d5a7917..fa62ef2 100644
--- a/25/streams/developer-guide/dsl-api.html
+++ b/25/streams/developer-guide/dsl-api.html
@@ -3736,7 +3736,7 @@ groupedTable
</div>
</div>
<div class="section" id="testing-a-streams-app">
- <a class="headerlink" href="#testing-a-streams-app"
title="Permalink to this headline"><h2>Testing a Streams application</h2></a>
+ <h2><a class="headerlink" href="#testing-a-streams-app"
title="Permalink to this headline">Testing a Streams application</a></h2>
Kafka Streams comes with a <code>test-utils</code> module to help
you test your application <a href="testing.html">here</a>.
</div>
</div>
diff --git a/25/streams/developer-guide/running-app.html
b/25/streams/developer-guide/running-app.html
index 4cf883e..2f4e2c0 100644
--- a/25/streams/developer-guide/running-app.html
+++ b/25/streams/developer-guide/running-app.html
@@ -51,7 +51,7 @@
<span id="streams-developer-guide-execution"></span><h1>Running
Streams Applications<a class="headerlink" href="#running-streams-applications"
title="Permalink to this headline"></a></h1>
<p>You can run Java applications that use the Kafka Streams library
without any additional configuration or requirements. Kafka Streams
also provides the ability to receive notification of the various
states of the application. The ability to monitor the runtime
- status is discussed in <a class="reference internal"
href="../monitoring.html#streams-monitoring"><span class="std std-ref">the
monitoring guide</span></a>.</p>
+ status is discussed in <a class="reference internal"
href="/documentation/#kafka_streams_monitoring"><span class="std std-ref">the
monitoring guide</span></a>.</p>
<div class="contents local topic" id="table-of-contents">
<p class="topic-title first"><b>Table of Contents</b></p>
<ul class="simple">
diff --git a/25/streams/developer-guide/write-streams.html
b/25/streams/developer-guide/write-streams.html
index a23fc9f..ed74d72 100644
--- a/25/streams/developer-guide/write-streams.html
+++ b/25/streams/developer-guide/write-streams.html
@@ -154,7 +154,7 @@
</div>
<p>If there are other instances of this stream processing application
running elsewhere (e.g., on another machine), Kafka
Streams transparently re-assigns tasks from the existing instances to
the new instance that you just started.
- For more information, see <a class="reference internal"
href="../architecture.html#streams_architecture_tasks"><span class="std
std-ref">Stream Partitions and Tasks</span></a> and <a class="reference
internal" href="../architecture.html#streams-architecture-threads"><span
class="std std-ref">Threading Model</span></a>.</p>
+ For more information, see <a class="reference internal"
href="../architecture.html#streams_architecture_tasks"><span class="std
std-ref">Stream Partitions and Tasks</span></a> and <a class="reference
internal" href="../architecture.html#streams_architecture_threads"><span
class="std std-ref">Threading Model</span></a>.</p>
<p>To catch any unexpected exceptions, you can set an <code
class="docutils literal"><span
class="pre">java.lang.Thread.UncaughtExceptionHandler</span></code> before you
start the
application. This handler is called whenever a stream thread is
terminated by an unexpected exception:</p>
<div class="highlight-java"><div
class="highlight"><pre><span></span><span class="c1">// Java 8+, using lambda
expressions</span>
@@ -208,7 +208,7 @@
</div>
<div class="section" id="testing-a-streams-app">
- <a class="headerlink" href="#testing-a-streams-app" title="Permalink
to this headline"><h2>Testing a Streams application</a></h2>
+ <h2><a class="headerlink" href="#testing-a-streams-app"
title="Permalink to this headline">Testing a Streams application</a></h2>
Kafka Streams comes with a <code>test-utils</code> module to help
you test your application <a href="testing.html">here</a>.
</div>
</div>
diff --git a/25/streams/upgrade-guide.html b/25/streams/upgrade-guide.html
index c6b9826..17fd5e9 100644
--- a/25/streams/upgrade-guide.html
+++ b/25/streams/upgrade-guide.html
@@ -34,7 +34,7 @@
</div>
<p>
- Upgrading from any older version to {{fullDotVersion}} is possible:
you will need to do two rolling bounces, where during the first rolling bounce
phase you set the config <code>upgrade.from="older version"</code>
+ Upgrading from any older version to {{fullDotVersion}} is possible: if
upgrading from 2.3 or below, you will need to do two rolling bounces, where
during the first rolling bounce phase you set the config
<code>upgrade.from="older version"</code>
(possible values are <code>"0.10.0" - "2.3"</code>) and during the
second you remove it. This is required to safely upgrade to the new cooperative
rebalancing protocol of the embedded consumer. Note that you will remain using
the old eager
rebalancing protocol if you skip or delay the second rolling bounce,
but you can safely switch over to cooperative at any time once the entire group
is on 2.4+ by removing the config value and bouncing. For more details please
refer to
<a href="https://cwiki.apache.org/confluence/x/vAclBg";>KIP-429</a>:
@@ -77,7 +77,7 @@
We add a new <code>cogroup()</code> operator (via <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-150+-+Kafka-Streams+Cogroup";>KIP-150</a>>)
that allows to aggregate multiple streams in a single operation.
Cogrouped streams can also be windowed before they are aggregated.
- We refer to the <a
href="/{{version}}/documentation/streams/developer-guide/dsl-api.html">developer
guide</a> for more details.
+ Please refer to the <a
href="/{{version}}/documentation/streams/developer-guide/dsl-api.html">developer
guide</a> for more details.
</p>
<p>
We added a new <code>KStream.toTable()</code> API to translate an
input event stream into a changelog stream as per
@@ -688,7 +688,7 @@
If you are monitoring on task level or processor-node / state store
level Streams metrics, please note that the metrics sensor name and hierarchy
was changed:
The task ids, store names and processor names are no longer in the
sensor metrics names, but instead are added as tags of the sensors to achieve
consistent metrics hierarchy.
As a result you may need to make corresponding code changes on your
metrics reporting and monitoring tools when upgrading to 1.0.0.
- Detailed metrics sensor can be found in the <a
href="#kafka_streams_monitoring">Streams Monitoring</a> section.
+ Detailed metrics sensor can be found in the <a
href="/{{version}}/documentation/#kafka_streams_monitoring">Streams
Monitoring</a> section.
</p>
<p>
