[kafka] branch 3.1 updated: MINOR: update docs note about spurious stream-stream join results (#13642)

[mj...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mjsax pushed a commit to branch 3.1
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/3.1 by this push:
     new a6ac997bbc9 MINOR: update docs note about spurious stream-stream join results (#13642)
a6ac997bbc9 is described below

commit a6ac997bbc991df326f9414b1f5e4d6a7fbb1bb2
Author: Victoria Xia <vi...@confluent.io>
AuthorDate: Tue Apr 25 22:41:23 2023 -0400

    MINOR: update docs note about spurious stream-stream join results (#13642)
    
    Reviewers: Matthias J. Sax <ma...@confluent.io>
---
 docs/streams/core-concepts.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/streams/core-concepts.html b/docs/streams/core-concepts.html
index 884b39898ed..319c981cc3e 100644
--- a/docs/streams/core-concepts.html
+++ b/docs/streams/core-concepts.html
@@ -332,7 +332,7 @@
     </p>
 
     <ul>
-        <li> For Stream-Stream joins, all three types (inner, outer, left) handle out-of-order records correctly, but the resulted stream may contain unnecessary leftRecord-null for left joins, and leftRecord-null or null-rightRecord for outer joins. </li>
+        <li> For Stream-Stream joins, all three types (inner, outer, left) handle out-of-order records correctly. </li>
         <li> For Stream-Table joins, out-of-order records are not handled (i.e., Streams applications don't check for out-of-order records and just process all records in offset order), and hence it may produce unpredictable results. </li>
         <li> For Table-Table joins, out-of-order records are not handled (i.e., Streams applications don't check for out-of-order records and just process all records in offset order). However, the join result is a changelog stream and hence will be eventually consistent. </li>
     </ul>