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

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


The following commit(s) were added to refs/heads/2.2 by this push:
     new 67dfa1d  HOTFIX: fix Kafka Streams upgrade note for broker backward 
compatibility (#7364)
67dfa1d is described below

commit 67dfa1d8225f2468a5f69218531703a72a63b1df
Author: Matthias J. Sax <[email protected]>
AuthorDate: Tue Sep 24 09:53:40 2019 -0700

    HOTFIX: fix Kafka Streams upgrade note for broker backward compatibility 
(#7364)
    
    Reviewer: Guozhang Wang <[email protected]>
---
 docs/streams/upgrade-guide.html | 12 ++++++++++--
 docs/upgrade.html               |  5 +++++
 2 files changed, 15 insertions(+), 2 deletions(-)

diff --git a/docs/streams/upgrade-guide.html b/docs/streams/upgrade-guide.html
index 660c4af..66cfee5 100644
--- a/docs/streams/upgrade-guide.html
+++ b/docs/streams/upgrade-guide.html
@@ -53,8 +53,10 @@
     </ul>
 
     <p>
-        Note, that a brokers must be on version 0.10.1 or higher to run a 
Kafka Streams application version 0.10.1 or higher;
-        On-disk message format must be 0.10 or higher to run a Kafka Streams 
application version 1.0 or higher.
+        To run a Kafka Streams application version 2.2.1 or higher a broker 
version 0.11.0 or higher is required
+        and the on-disk message format must be 0.11 or higher.
+        Brokers must be on version 0.10.1 or higher to run a Kafka Streams 
application version 0.10.1 to 2.2.0.
+        Additionally, on-disk message format must be 0.10 or higher to run a 
Kafka Streams application version 1.0 to 2.2.0.
         For Kafka Streams 0.10.0, broker version 0.10.0 or higher is required.
     </p>
 
@@ -70,6 +72,12 @@
         More details about the new config 
<code>StreamsConfig#TOPOLOGY_OPTIMIZATION</code> can be found in <a 
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-295%3A+Add+Streams+Configuration+Allowing+for+Optional+Topology+Optimization";>KIP-295</a>.
     </p>
 
+    <h3><a id="streams_notable_changes_221" 
href="#streams_api_changes_221">Notable changes in Kafka Streams 2.2.1</a></h3>
+    <p>
+        As of Kafka Streams 2.2.1 a message format 0.11 or higher is required;
+        this implies that brokers must be on version 0.11.0 or higher.
+    </p>
+
     <h3><a id="streams_api_changes_220" 
href="#streams_api_changes_220">Streams API changes in 2.2.0</a></h3>
     <p>
         We've simplified the <code>KafkaStreams#state</code> transition 
diagram during the starting up phase a bit in 2.2.0: in older versions the 
state will transit from <code>CREATED</code> to <code>RUNNING</code>, and then 
to <code>REBALANCING</code> to get the first
diff --git a/docs/upgrade.html b/docs/upgrade.html
index 1828ab7..5c473ed 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -61,6 +61,11 @@
     </li>
 </ol>
 
+<h5><a id="upgrade_221_notable" href="#upgrade_221_notable">Notable changes in 
2.2.1</a></h5>
+<ul>
+    <li>Kafka Streams 2.2.1 requires 0.11 message format or higher and does 
not work with older message format.</li>
+</ul>
+
 <h5><a id="upgrade_220_notable" href="#upgrade_220_notable">Notable changes in 
2.2.0</a></h5>
 <ul>
     <li>The default consumer group id has been changed from the empty string 
(<code>""</code>) to <code>null</code>. Consumers who use the new default group 
id will not be able to subscribe to topics,

Reply via email to