You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by mj...@apache.org on 2023/12/19 09:26:24 UTC
(kafka) branch trunk updated: MINOR: doc/streams/dsl-api, fix href of "KTable-KTable Foreign-Key Joins" (#13919)
This is an automated email from the ASF dual-hosted git repository.
mjsax pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new 55be0b3d4e8 MINOR: doc/streams/dsl-api, fix href of "KTable-KTable Foreign-Key Joins" (#13919)
55be0b3d4e8 is described below
commit 55be0b3d4e81f6c934f666746e7505b43b552431
Author: Iblis Lin <ib...@apache.org>
AuthorDate: Tue Dec 19 17:26:17 2023 +0800
MINOR: doc/streams/dsl-api, fix href of "KTable-KTable Foreign-Key Joins" (#13919)
Reviewers: Matthias J. Sax <ma...@confluent.io>
---
docs/streams/developer-guide/dsl-api.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/streams/developer-guide/dsl-api.html b/docs/streams/developer-guide/dsl-api.html
index cc729ee25c2..bb6954102d2 100644
--- a/docs/streams/developer-guide/dsl-api.html
+++ b/docs/streams/developer-guide/dsl-api.html
@@ -1699,7 +1699,7 @@ KTable<String, Integer> aggregated = groupedTable.aggregate(
<p>For equi-joins, input data must be co-partitioned when joining. This ensures that input records with the same key from both sides of the
join, are delivered to the same stream task during processing.
<strong>It is your responsibility to ensure data co-partitioning when joining</strong>.
- Co-partitioning is not required when performing <a class="reference internal" href="#streams-developer-guide-dsl-joins-ktable-ktable-fk-join"><span class="std std-ref">KTable-KTable Foreign-Key joins</span></a> and <a class="reference internal" href="#streams_concepts_globalktable"><span class="std std-ref">Global KTable joins</span></a>.
+ Co-partitioning is not required when performing <a class="reference internal" href="#ktable-ktable-fk-join"><span class="std std-ref">KTable-KTable Foreign-Key joins</span></a> and <a class="reference internal" href="#streams_concepts_globalktable"><span class="std std-ref">Global KTable joins</span></a>.
</p>
<p>The requirements for data co-partitioning are:</p>
<ul class="simple">
@@ -1724,7 +1724,7 @@ KTable<String, Integer> aggregated = groupedTable.aggregate(
not required because <em>all</em> partitions of the <code class="docutils literal"><span class="pre">GlobalKTable</span></code>‘s underlying changelog stream are made available to
each <code class="docutils literal"><span class="pre">KafkaStreams</span></code> instance. That is, each instance has a full copy of the changelog stream. Further, a
<code class="docutils literal"><span class="pre">KeyValueMapper</span></code> allows for non-key based joins from the <code class="docutils literal"><span class="pre">KStream</span></code> to the <code class="docutils literal"><span class="pre">GlobalKTable</span></code>.
- <a class="reference internal" href="#streams-developer-guide-dsl-joins-ktable-ktable-fk-join"><span class="std std-ref">KTable-KTable Foreign-Key joins</span></a> also do not require co-partitioning. Kafka Streams internally ensures co-partitioning for Foreign-Key joins.
+ <a class="reference internal" href="#ktable-ktable-fk-join"><span class="std std-ref">KTable-KTable Foreign-Key joins</span></a> also do not require co-partitioning. Kafka Streams internally ensures co-partitioning for Foreign-Key joins.
</p>
<div class="admonition note">