This is an automated email from the ASF dual-hosted git repository.
srdo pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/storm-site.git
commit 1f0067b65e0d3ec47904d06ce80bb34fb8fe4ba3
Author: Stig Rohde Døssing <stigdoess...@gmail.com>
AuthorDate: Fri Jul 19 19:11:15 2019 +0200
Rebuild site
---
content/2019/05/30/storm200-released.html | 2 +-
content/feed.xml | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/2019/05/30/storm200-released.html
b/content/2019/05/30/storm200-released.html
index de3c77b..0f5c4d6 100644
--- a/content/2019/05/30/storm200-released.html
+++ b/content/2019/05/30/storm200-released.html
@@ -262,7 +262,7 @@
<p>The most significant change to Storm's Kafka integration since 1.x, is
that storm-kafka has been removed. The module was deprecated a while back, due
to Kafka's deprecation of the underlying client library. Users will have to
move to the storm-kafka-client module, which uses Kafka's ´kafka-clients´
library for integration.</p>
-<p>For the most part, the migration to storm-kafka-client is straightforward.
The documentation for storm-kafka-client contains a helpful mapping between the
old and new spout configurations. If you are using any of the storm-kafka
spouts, you will need to migrate offset checkpoints to the new spout, to avoid
the new spout starting from scratch on your partitions. Storm provides a helper
tool to do this which can be found <a
href="fhttps://github.com/apache/storm/tree/master/external/sto [...]
+<p>For the most part, the migration to storm-kafka-client is straightforward.
The documentation for storm-kafka-client contains a helpful mapping between the
old and new spout configurations. If you are using any of the storm-kafka
spouts, you will need to migrate offset checkpoints to the new spout, to avoid
the new spout starting from scratch on your partitions. Storm provides a helper
tool to do this which can be found <a
href="https://github.com/apache/storm/tree/master/external/stor [...]
<p>When performing a migration, you should stop your topology, run the
migration tool, then redeploy your topology with the storm-kafka-client
spout.</p>
diff --git a/content/feed.xml b/content/feed.xml
index 440c1c4..9e2ea3e 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -5,8 +5,8 @@
<description></description>
<link>http://storm.apache.org/</link>
<atom:link href="http://storm.apache.org/feed.xml"; rel="self"
type="application/rss+xml"/>
- <pubDate>Thu, 18 Jul 2019 22:29:01 +0200</pubDate>
- <lastBuildDate>Thu, 18 Jul 2019 22:29:01 +0200</lastBuildDate>
+ <pubDate>Fri, 19 Jul 2019 19:07:38 +0200</pubDate>
+ <lastBuildDate>Fri, 19 Jul 2019 19:07:38 +0200</lastBuildDate>
<generator>Jekyll v3.6.2</generator>
<item>
@@ -121,7 +121,7 @@
<p>The most significant change to Storm&#39;s Kafka integration
since 1.x, is that storm-kafka has been removed. The module was deprecated a
while back, due to Kafka&#39;s deprecation of the underlying client
library. Users will have to move to the storm-kafka-client module, which uses
Kafka&#39;s ´kafka-clients´ library for integration.</p>
-<p>For the most part, the migration to storm-kafka-client is
straightforward. The documentation for storm-kafka-client contains a helpful
mapping between the old and new spout configurations. If you are using any of
the storm-kafka spouts, you will need to migrate offset checkpoints to the new
spout, to avoid the new spout starting from scratch on your partitions. Storm
provides a helper tool to do this which can be found <a
href="fhttps://github.com/apache/storm/tree/maste [...]
+<p>For the most part, the migration to storm-kafka-client is
straightforward. The documentation for storm-kafka-client contains a helpful
mapping between the old and new spout configurations. If you are using any of
the storm-kafka spouts, you will need to migrate offset checkpoints to the new
spout, to avoid the new spout starting from scratch on your partitions. Storm
provides a helper tool to do this which can be found <a
href="https://github.com/apache/storm/tree/master [...]
<p>When performing a migration, you should stop your topology, run the
migration tool, then redeploy your topology with the storm-kafka-client
spout.</p>
