kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From guozh...@apache.org
Subject kafka git commit: HOTFIX: Add missing template ref in upgrade section
Date Fri, 03 Nov 2017 17:11:19 GMT
Repository: kafka
Updated Branches:
  refs/heads/1.0 c3d8bcc2d -> 82292faac


HOTFIX: Add missing template ref in upgrade section


Project: http://git-wip-us.apache.org/repos/asf/kafka/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/82292faa
Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/82292faa
Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/82292faa

Branch: refs/heads/1.0
Commit: 82292faac79e2a0c63c216cb2f91cde7c596ad9e
Parents: c3d8bcc
Author: Guozhang Wang <wangguoz@gmail.com>
Authored: Fri Nov 3 10:10:35 2017 -0700
Committer: Guozhang Wang <wangguoz@gmail.com>
Committed: Fri Nov 3 10:11:08 2017 -0700

----------------------------------------------------------------------
 docs/upgrade.html | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka/blob/82292faa/docs/upgrade.html
----------------------------------------------------------------------
diff --git a/docs/upgrade.html b/docs/upgrade.html
index f5380e8..eed0bc4 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -17,6 +17,8 @@
 
 <script><!--#include virtual="js/templateData.js" --></script>
 
+<script id="upgrade-template" type="text/x-handlebars-template">
+
 <h4><a id="upgrade_1_0_0" href="#upgrade_1_0_0">Upgrading from 0.8.x, 0.9.x,
0.10.0.x, 0.10.1.x, 0.10.2.x or 0.11.0.x to 1.0.0</a></h4>
 <p>Kafka 1.0.0 introduces wire protocol changes. By following the recommended rolling
upgrade plan below,
     you guarantee no downtime during the upgrade. However, please review the <a href="#upgrade_100_notable">notable
changes in 1.0.0</a> before upgrading.
@@ -112,7 +114,7 @@
     <li> If you are monitoring on streams metrics, you will need make some changes
to the metrics names in your reporting and monitoring code, because the metrics sensor hierarchy
was changed. </li>
     <li> There are a few public APIs including <code>ProcessorContext#schedule()</code>,
<code>Processor#punctuate()</code> and <code>KStreamBuilder</code>,
<code>TopologyBuilder</code> are being deprecated by new APIs.
         We recommend making corresponding code changes, which should be very minor since
the new APIs look quite similar, when you upgrade.
-    <li> See <a href="/{{version}}/documentation/streams#streams_api_changes_100">Streams
API changes in 1.0.0</a> for more details. </li>
+    <li> See <a href="/{{version}}/documentation/streams/upgrade-guide#streams_api_changes_100">Streams
API changes in 1.0.0</a> for more details. </li>
 </ul>
 
 <h4><a id="upgrade_11_0_0" href="#upgrade_11_0_0">Upgrading from 0.8.x, 0.9.x,
0.10.0.x, 0.10.1.x or 0.10.2.x to 0.11.0.0</a></h4>
@@ -160,6 +162,14 @@
     before you switch to 0.11.0.</li>
 </ol>
 
+<h5><a id="upgrade_1100_streams" href="#upgrade_1100_streams">Upgrading a 0.10.2
Kafka Streams Application</a></h5>
+<ul>
+    <li> Upgrading your Streams application from 0.10.2 to 0.11.0 does not require
a broker upgrade.
+        A Kafka Streams 0.11.0 application can connect to 0.11.0, 0.10.2 and 0.10.1 brokers
(it is not possible to connect to 0.10.0 brokers though). </li>
+    <li> If you specify customized <code>key.serde</code>, <code>value.serde</code>
and <code>timestamp.extractor</code> in configs, it is recommended to use their
replaced configure parameter as these configs are deprecated. </li>
+    <li> See <a href="/{{version}}/documentation/streams/upgrade-guide#streams_api_changes_0110">Streams
API changes in 0.11.0</a> for more details. </li>
+</ul>
+
 <h5><a id="upgrade_1100_notable" href="#upgrade_1100_notable">Notable changes
in 0.11.0.0</a></h5>
 <ul>
     <li>Unclean leader election is now disabled by default. The new default favors
durability over availability. Users who wish to
@@ -307,7 +317,7 @@ Kafka cluster before upgrading your clients. Version 0.10.2 brokers support
0.8.
     <li> You need to recompile your code. Just swapping the Kafka Streams library jar
file will not work and will break your application. </li>
     <li> If you use a custom (i.e., user implemented) timestamp extractor, you will
need to update this code, because the <code>TimestampExtractor</code> interface
was changed. </li>
     <li> If you register custom metrics, you will need to update this code, because
the <code>StreamsMetric</code> interface was changed. </li>
-    <li> See <a href="/{{version}}/documentation/streams#streams_api_changes_0102">Streams
API changes in 0.10.2</a> for more details. </li>
+    <li> See <a href="/{{version}}/documentation/streams/upgrade-guide#streams_api_changes_0102">Streams
API changes in 0.10.2</a> for more details. </li>
 </ul>
 
 <h5><a id="upgrade_10201_notable" href="#upgrade_10201_notable">Notable changes
in 0.10.2.1</a></h5>
@@ -386,7 +396,7 @@ only support 0.10.1.x or later brokers while 0.10.1.x brokers also support
older
 <h5><a id="upgrade_1010_streams" href="#upgrade_1010_streams">Upgrading a 0.10.0
Kafka Streams Application</a></h5>
 <ul>
     <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).
+    <li> There are couple of API changes, that are not backward compatible (cf. <a
href="/{{version}}/documentation/streams/upgrade-guide#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>
 </ul>
 


Mime
View raw message