Browse Source

MINOR: update for 0.10.2.2 release (#5327)

Reviewer: Guozhang Wang <guozhang@confluent.io>
pull/5424/head
Matthias J. Sax 6 years ago committed by GitHub
parent
commit
060fd7c5cc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      docs/upgrade.html

2
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 @@ -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 @@ -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>

Loading…
Cancel
Save