[
https://issues.apache.org/jira/browse/KAFKA-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438768#comment-16438768
]
ASF GitHub Bot commented on KAFKA-6790:
---------------------------------------
guozhangwang closed pull request #4874: KAFKA-6790
URL: https://github.com/apache/kafka/pull/4874
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/docs/streams/core-concepts.html b/docs/streams/core-concepts.html
index 889fe06c45f..16502879d6b 100644
--- a/docs/streams/core-concepts.html
+++ b/docs/streams/core-concepts.html
@@ -63,7 +63,7 @@ <h3><a id="streams_topology" href="#streams_topology">Stream
Processing Topology
<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 6c6fd2f76cc..a73a814be11 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 this example is
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Broken link in documentation for processor nodes
> ------------------------------------------------
>
> Key: KAFKA-6790
> URL: https://issues.apache.org/jira/browse/KAFKA-6790
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: robin m
> Priority: Major
> Fix For: 1.1.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
