This is an automated email from the ASF dual-hosted git repository.
guozhang pushed a commit to branch 1.0
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/1.0 by this push:
new 77b1a35 KAFKA-6790: Fix Streams processor node broken link (#4874)
77b1a35 is described below
commit 77b1a357ba147da37ca534df6a4c6bdf76aafb4c
Author: ro7m <[email protected]>
AuthorDate: Sun Apr 15 22:26:12 2018 +0530
KAFKA-6790: Fix Streams processor node broken link (#4874)
The page here
https://kafka.apache.org/11/documentation/streams/developer-guide/memory-mgmt.html
talks about processor nodes and refers to non existing links.
Broken link (appears twice in the same document):
https://kafka.apache.org/11/documentation/streams/concepts.html#streams-concepts-processor
To find this search for the word "processor node" on the page
memory-management , the ones which are links are broken.
Reviewers: Guozhang Wang <[email protected]>
---
docs/streams/core-concepts.html | 2 +-
docs/streams/developer-guide/memory-mgmt.html | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/streams/core-concepts.html b/docs/streams/core-concepts.html
index d803b3a..f2f32ad 100644
--- a/docs/streams/core-concepts.html
+++ b/docs/streams/core-concepts.html
@@ -63,7 +63,7 @@
<ul>
<li>A <b>stream</b> is the most important abstraction provided by
Kafka Streams: it represents an unbounded, continuously updating data set. A
stream is an ordered, replayable, and fault-tolerant sequence of immutable data
records, where a <b>data record</b> is defined as a key-value pair.</li>
<li>A <b>stream processing application</b> is any program that makes
use of the Kafka Streams library. It defines its computational logic through
one or more <b>processor topologies</b>, where a processor topology is a graph
of stream processors (nodes) that are connected by streams (edges).</li>
- <li>A <b>stream processor</b> is a node in the processor topology; it
represents a processing step to transform data in streams by receiving one
input record at a time from its upstream processors in the topology, applying
its operation to it, and may subsequently produce one or more output records to
its downstream processors. </li>
+ <li>A <b><a href="#streams_processor_node">stream processor</a></b> is
a node in the processor topology; it represents a processing step to transform
data in streams by receiving one input record at a time from its upstream
processors in the topology, applying its operation to it, and may subsequently
produce one or more output records to its downstream processors. </li>
</ul>
There are two special processors in the topology:
diff --git a/docs/streams/developer-guide/memory-mgmt.html
b/docs/streams/developer-guide/memory-mgmt.html
index b9ee1f3..e3a1033 100644
--- a/docs/streams/developer-guide/memory-mgmt.html
+++ b/docs/streams/developer-guide/memory-mgmt.html
@@ -55,9 +55,9 @@
<p>For such <code class="docutils literal"><span
class="pre">KTable</span></code> instances, the record cache is used for:</p>
<ul class="simple">
<li>Internal caching and compacting of output records before they are
written by the underlying stateful
- <a class="reference internal"
href="../concepts.html#streams-concepts-processor"><span class="std
std-ref">processor node</span></a> to its internal state stores.</li>
+ <a class="reference internal"
href="../core-concepts#streams_processor_node"><span class="std
std-ref">processor node</span></a> to its internal state stores.</li>
<li>Internal caching and compacting of output records before they are
forwarded from the underlying stateful
- <a class="reference internal"
href="../concepts.html#streams-concepts-processor"><span class="std
std-ref">processor node</span></a> to any of its downstream processor
nodes.</li>
+ <a class="reference internal"
href="../core-concepts#streams_processor_node"><span class="std
std-ref">processor node</span></a> to any of its downstream processor
nodes.</li>
</ul>
<p>Use the following example to understand the behaviors with and
without record caching. In this example, the input is a
<code class="docutils literal"><span
class="pre">KStream<String,</span> <span
class="pre">Integer></span></code> with the records <code class="docutils
literal"><span class="pre"><K,V>:</span> <span class="pre"><A,</span>
<span class="pre">1>,</span> <span class="pre"><D,</span> <span
class="pre">5>,</span> <span class="pre"><A,</span> <span
class="pre">20>,</span> <span class="pre"><A,</span> <span
class="pre">300></span></code>. The focus in [...]
--
To stop receiving notification emails like this one, please contact
[email protected].
