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 2021/04/09 19:16:05 UTC
[kafka] branch 2.8 updated (e399a80 -> cea1528)
This is an automated email from the ASF dual-hosted git repository.
mjsax pushed a change to branch 2.8
in repository https://gitbox.apache.org/repos/asf/kafka.git.
from e399a80 KAFKA-12619; Raft leader should expose hw only after committing LeaderChange (#10481)
new 893bd88 MINOR: Fix left/outer join descriptions in Streams DSL reference topic (#10453)
new cea1528 MINOR: Fix typo in docs (#10423)
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/quickstart.html | 2 +-
docs/streams/developer-guide/dsl-api.html | 16 +++++++++-------
2 files changed, 10 insertions(+), 8 deletions(-)
[kafka] 02/02: MINOR: Fix typo in docs (#10423)
Posted by mj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mjsax pushed a commit to branch 2.8
in repository https://gitbox.apache.org/repos/asf/kafka.git
commit cea1528666bcc7180909c4376f10e2f683d7476d
Author: Andrew Lee <al...@gmail.com>
AuthorDate: Fri Apr 9 12:12:52 2021 -0700
MINOR: Fix typo in docs (#10423)
Reviewers: Matthias J. Sax <ma...@confluent.io>
---
docs/quickstart.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/quickstart.html b/docs/quickstart.html
index 5e2a1d9..f204be3 100644
--- a/docs/quickstart.html
+++ b/docs/quickstart.html
@@ -166,7 +166,7 @@ This is my second event</code></pre>
</p>
<p>Take a look at the <a href="/documentation/#connect">Kafka Connect section</a>
- learn more about how to continuously import/export your data into and out of Kafka.</p>
+ to learn more about how to continuously import/export your data into and out of Kafka.</p>
</div>
[kafka] 01/02: MINOR: Fix left/outer join descriptions in Streams
DSL reference topic (#10453)
Posted by mj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mjsax pushed a commit to branch 2.8
in repository https://gitbox.apache.org/repos/asf/kafka.git
commit 893bd88f170f26df47ba8a03bcc976903229b0bd
Author: Jim Galasyn <ji...@confluent.io>
AuthorDate: Fri Apr 9 11:41:52 2021 -0700
MINOR: Fix left/outer join descriptions in Streams DSL reference topic (#10453)
Reviewer: Matthias J. Sax <ma...@confluent.io>
---
docs/streams/developer-guide/dsl-api.html | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/docs/streams/developer-guide/dsl-api.html b/docs/streams/developer-guide/dsl-api.html
index 3c885d6..84fe4e7ff 100644
--- a/docs/streams/developer-guide/dsl-api.html
+++ b/docs/streams/developer-guide/dsl-api.html
@@ -2232,8 +2232,8 @@ Map<String, KStream<String, Long>> branches =
<blockquote>
<div><ul class="simple">
<li>Input records with a <code class="docutils literal"><span class="pre">null</span></code> key are ignored and do not trigger the join.</li>
- <li>Input records with a <code class="docutils literal"><span class="pre">null</span></code> value are interpreted as <em>tombstones</em> for the corresponding key, which indicate the deletion of the key from the table. Tombstones do not
- trigger the join. When an input tombstone is received, then an output tombstone is forwarded directly to the join result KTable if required (i.e. only if the corresponding
+ <li>Input records with a <code class="docutils literal"><span class="pre">null</span></code> value are interpreted as <em>tombstones</em> for the corresponding key, which indicate the deletion of the key from the table. Right-tombstones trigger the join,
+ but left-tombstones don't: when an input tombstone is received, an output tombstone is forwarded directly to the join result KTable if required (i.e. only if the corresponding
key actually exists already in the join result KTable).</li>
</ul>
</div></blockquote>
@@ -2280,8 +2280,8 @@ Map<String, KStream<String, Long>> branches =
<blockquote>
<div><ul class="simple">
<li>Input records with a <code class="docutils literal"><span class="pre">null</span></code> key are ignored and do not trigger the join.</li>
- <li>Input records with a <code class="docutils literal"><span class="pre">null</span></code> value are interpreted as <em>tombstones</em> for the corresponding key, which indicate the deletion of the key from the table. Tombstones do not
- trigger the join. When an input tombstone is received, then an output tombstone is forwarded directly to the join result KTable if required (i.e. only if the corresponding
+ <li>Input records with a <code class="docutils literal"><span class="pre">null</span></code> value are interpreted as <em>tombstones</em> for the corresponding key, which indicate the deletion of the key from the table. Tombstones may trigger joins,
+ depending on the content in the left and right tables. When an input tombstone is received, an output tombstone is forwarded directly to the join result KTable if required (i.e. only if the corresponding
key actually exists already in the join result KTable).</li>
</ul>
</div></blockquote>
@@ -2515,7 +2515,8 @@ Map<String, KStream<String, Long>> branches =
literal"><span class="pre">null</span></code>
value are interpreted as <em>tombstones</em>
for the corresponding key, which indicate the
- deletion of the key from the table. When an input
+ deletion of the key from the table. Tombstones do not
+ trigger the join. When an input
tombstone is received, then an output
tombstone is forwarded directly to the join
result KTable if required (i.e. only if the
@@ -2574,8 +2575,9 @@ Map<String, KStream<String, Long>> branches =
literal"><span class="pre">null</span></code>
value are interpreted as <em>tombstones</em>
for the corresponding key, which indicate the
- deletion of the key from the table. When an input
- tombstone is received, then an output
+ deletion of the key from the table. Right-tombstones
+ trigger the join, but left-tombstones don't:
+ when an input tombstone is received, then an output
tombstone is forwarded directly to the join
result KTable if required (i.e. only if the
corresponding key actually exists already in