kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From guozh...@apache.org
Subject kafka-site git commit: Add the missing streams upgrade paragraph, fix a few broken links
Date Fri, 03 Nov 2017 16:56:46 GMT
Repository: kafka-site
Updated Branches:
  refs/heads/asf-site 5badc890e -> afd3a6eb7


Add the missing streams upgrade paragraph, fix a few broken links


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

Branch: refs/heads/asf-site
Commit: afd3a6eb7e13f1a673b83952d0cfaf0316d6b943
Parents: 5badc89
Author: Guozhang Wang <wangguoz@gmail.com>
Authored: Fri Nov 3 09:56:37 2017 -0700
Committer: Guozhang Wang <wangguoz@gmail.com>
Committed: Fri Nov 3 09:56:37 2017 -0700

----------------------------------------------------------------------
 0102/upgrade.html |  4 ++--
 0110/upgrade.html | 13 +++++++++++--
 10/upgrade.html   |  8 ++++++++
 3 files changed, 21 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka-site/blob/afd3a6eb/0102/upgrade.html
----------------------------------------------------------------------
diff --git a/0102/upgrade.html b/0102/upgrade.html
index d7581fa..ade953c 100644
--- a/0102/upgrade.html
+++ b/0102/upgrade.html
@@ -58,7 +58,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>
@@ -139,7 +139,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>
 

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/afd3a6eb/0110/upgrade.html
----------------------------------------------------------------------
diff --git a/0110/upgrade.html b/0110/upgrade.html
index 9f0dbdf..c9ddc60 100644
--- a/0110/upgrade.html
+++ b/0110/upgrade.html
@@ -64,6 +64,15 @@
     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
@@ -211,7 +220,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>
@@ -292,7 +301,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>
 

http://git-wip-us.apache.org/repos/asf/kafka-site/blob/afd3a6eb/10/upgrade.html
----------------------------------------------------------------------
diff --git a/10/upgrade.html b/10/upgrade.html
index e21a7c5..eed0bc4 100644
--- a/10/upgrade.html
+++ b/10/upgrade.html
@@ -162,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


Mime
View raw message