kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mj...@apache.org
Subject [kafka] branch 0.10.2 updated: MINOR: update for 0.10.2.2 release (#5327)
Date Tue, 03 Jul 2018 20:44:27 GMT
This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/0.10.2 by this push:
     new 060fd7c  MINOR: update for 0.10.2.2 release (#5327)
060fd7c is described below

commit 060fd7c5cc2a34d43871af8452a07a84ee32bd20
Author: Matthias J. Sax <mjsax@apache.org>
AuthorDate: Tue Jul 3 13:44:22 2018 -0700

    MINOR: update for 0.10.2.2 release (#5327)
    
    Reviewer: Guozhang Wang <guozhang@confluent.io>
---
 docs/upgrade.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/upgrade.html b/docs/upgrade.html
index 825e249..5db484f 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -146,6 +146,7 @@ only support 0.10.1.x or later brokers while 0.10.1.x brokers also support
older
     <li> Upgrading your Streams application from 0.10.0 to 0.10.1 does require a <a
href="#upgrade_10_1">broker upgrade</a> because a Kafka Streams 0.10.1 application
can only connect to 0.10.1 brokers. </li>
     <li> There are couple of API changes, that are not backward compatible (cf. <a
href="/{{version}}/documentation/streams#streams_api_changes_0101">Streams API changes
in 0.10.1</a> for more details).
          Thus, you need to update and recompile your code. Just swapping the Kafka Streams
library jar file will not work and will break your application. </li>
+<!-- TODO add when 0.10.1.2 is released
     <li> Upgrading from 0.10.0.x to 0.10.1.2 requires two rolling bounces with config
<code>upgrade.from="0.10.0"</code> set for first upgrade phase
          (cf. <a href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-268%3A+Simplify+Kafka+Streams+Rebalance+Metadata+Upgrade">KIP-268</a>).
          As an alternative, an offline upgrade is also possible.
@@ -156,6 +157,7 @@ only support 0.10.1.x or later brokers while 0.10.1.x brokers also support
older
             <li> bounce each instance of your application once more to complete the
upgrade </li>
         </ul>
     </li>
+-->
     <li> Upgrading from 0.10.0.x to 0.10.1.0 or 0.10.1.1 requires an offline upgrade
(rolling bounce upgrade is not supported)
         <ul>
             <li> stop all old (0.10.0.x) application instances </li>


Mime
View raw message