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

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


The following commit(s) were added to refs/heads/asf-site by this push:
     new d3fe4b4  MINOR: improve versions (#151)
d3fe4b4 is described below

commit d3fe4b462a806ec10446ff17018698c0f8f9e83b
Author: Matthias J. Sax <[email protected]>
AuthorDate: Wed Jul 18 13:43:34 2018 -0700

    MINOR: improve versions (#151)
    
    Reviewer: Guozhang Wang <[email protected]>
---
 10/upgrade.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/10/upgrade.html b/10/upgrade.html
index 2d53cd5..639ccc8 100644
--- a/10/upgrade.html
+++ b/10/upgrade.html
@@ -131,8 +131,8 @@
 
 <h5><a id="upgrade_100_streams_from_0110" 
href="#upgrade_100_streams_from_0110">Upgrading a 0.11.0 Kafka Streams 
Application</a></h5>
 <ul>
-    <li> Upgrading your Streams application from 0.11.0 to 1.0.0 does not 
require a broker upgrade.
-         A Kafka Streams 1.0.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> Upgrading your Streams application from 0.11.0 to 1.0 does not 
require a broker upgrade.
+         A Kafka Streams 1.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).
          However, Kafka Streams 1.0 requires 0.10 message format or newer and 
does not work with older message formats. </li>
     <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.

Reply via email to