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 bb159a3ba019bb2106dd3cd252fd16128ef8fd94
Author: Stig Rohde Døssing <stigdoess...@gmail.com>
AuthorDate: Thu May 30 23:25:11 2019 +0200
Rebuild content
---
content/2019/05/30/storm200-released.html | 27 +++++++++---
content/feed.xml | 51 ++++++++++++++--------
content/releases.html | 56 ++++++++++++-------------
content/releases/1.2.2/metrics_v2.html | 2 +-
content/releases/2.0.0-SNAPSHOT/metrics_v2.html | 2 +-
content/releases/current/metrics_v2.html | 2 +-
6 files changed, 87 insertions(+), 53 deletions(-)
diff --git a/content/2019/05/30/storm200-released.html
b/content/2019/05/30/storm200-released.html
index 5f93f20..fd5b6a0 100644
--- a/content/2019/05/30/storm200-released.html
+++ b/content/2019/05/30/storm200-released.html
@@ -296,22 +296,21 @@
<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="fhttps://github.com/apache/storm/tree/master/external/sto [...]
<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>
<h3 id="move-to-using-the-kafkaconsumer-assign-api">Move to Using the
KafkaConsumer.assign API</h3>
-<p>Storm-kafka-client in Storm 1.x allowed you to use Kafka's own
mechanism to manage which spout tasks were responsible for which partitions.
This mechanism was a poor fit for Storm, and was deprecated in 1.2.0. It has
been <a href="https://issues.apache.org/jira/browse/STORM-2542.";>removed
entirely in 2.0</a></p>
+<p>Storm-kafka-client in Storm 1.x allowed you to use Kafka's own
mechanism to manage which spout tasks were responsible for which partitions.
This mechanism was a poor fit for Storm, and was deprecated in 1.2.0. It has
been <a href="https://issues.apache.org/jira/browse/STORM-2542";>removed
entirely in 2.0</a>.</p>
<p>The storm-kafka-client Subscription interface has also been removed. It
offered too limited control over the subscription behavior. It has been
replaced with the TopicFilter and ManualPartitioner interfaces. Unless you were
using a custom Subscription implementation, this will likely not
-affect you. If you were using a custom Subscription, <a
href="https://github.com/apache/storm/blob/master/docs/storm-kafka-client.md#manual-partition-assigment-advanced";>the
storm-kafka-client documentation describes how to customize assignment</a>
-.</p>
+affect you. If you were using a custom Subscription, <a
href="https://github.com/apache/storm/blob/master/docs/storm-kafka-client.md#manual-partition-assigment-advanced";>the
storm-kafka-client documentation describes how to customize assignment</a>.</p>
<h3 id="other-kafka-highlights">Other Kafka Highlights</h3>
<ul>
-<li>The KafkaBolt now allows you to <a
href="https://issues.apache.org/jira/browse/STORM-3175.";>specify a callback
that will be called when a batch is written to Kafka</a></li>
+<li>The KafkaBolt now allows you to <a
href="https://issues.apache.org/jira/browse/STORM-3175";>specify a callback that
will be called when a batch is written to Kafka</a>.</li>
<li>The FirstPollOffsetStrategy behavior has been made consistent between the
non-Trident and Trident spouts. It is now always the case that EARLIEST/LATEST
only take effect on topology redeploy, and not when a worker restarts <a
href="https://issues.apache.org/jira/browse/STORM-2990";>https://issues.apache.org/jira/browse/STORM-2990</a>.</li>
<li>Storm-kafka-client now has a transactional non-opaque Trident spout <a
href="https://issues.apache.org/jira/browse/STORM-2974";>https://issues.apache.org/jira/browse/STORM-2974</a>.</li>
<li>There are new example modules for storm-kafka-client. You can find them <a
href="https://github.com/apache/storm/tree/master/examples/storm-kafka-client-examples";>here</a>.</li>
@@ -322,6 +321,24 @@ affect you. If you were using a custom Subscription, <a
href="https://github.com
<p>With the release of 2.0.0 the 1.0.x version line will no longer be
maintained. 1.0.x users are strongly encouraged to upgrade to a more recent
release.</p>
+<h2 id="move-to-java-8">Move to Java 8</h2>
+
+<p>Java 7 support has been dropped, and Storm 2.0.0 requires Java 8.</p>
+
+<h2 id="reorganization-of-storm-maven-artifacts">Reorganization of Storm Maven
artifacts</h2>
+
+<p>The storm-core artifact has <a
href="https://issues.apache.org/jira/browse/STORM-2441";>been split</a> into
client and server-facing parts. Topology jars should depend on the following
artifact as of Storm 2.0.0:</p>
+<div class="highlight"><pre><code class="language-"
data-lang=""><groupId>org.apache.storm</groupId>
+<artifactId>storm-client</artifactId>
+<version>2.0.0</version>
+<scope>provided</scope>
+</code></pre></div>
+<p>Projects using <code>LocalCluster</code> for testing will additionally need
to depend on the Storm server jar:</p>
+<div class="highlight"><pre><code class="language-"
data-lang=""><groupId>org.apache.storm</groupId>
+<artifactId>storm-server</artifactId>
+<version>2.0.0</version>
+<scope>test</scope>
+</code></pre></div>
<h2 id="stay-tuned">Stay Tuned</h2>
<p>Keep an eye on the Apache Storm blog for additional posts by Storm
contributors for more in-depth discussions of new features in Storm 2.0.0
including:</p>
diff --git a/content/feed.xml b/content/feed.xml
index 4b8417d..96d5269 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, 30 May 2019 15:40:04 -0400</pubDate>
- <lastBuildDate>Thu, 30 May 2019 15:40:04 -0400</lastBuildDate>
+ <pubDate>Thu, 30 May 2019 23:19:08 +0200</pubDate>
+ <lastBuildDate>Thu, 30 May 2019 23:19:08 +0200</lastBuildDate>
<generator>Jekyll v3.6.2</generator>
<item>
@@ -43,22 +43,21 @@
<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="fhttps://github.com/apache/storm/tree/maste [...]
<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>
<h3 id="move-to-using-the-kafkaconsumer-assign-api">Move to
Using the KafkaConsumer.assign API</h3>
-<p>Storm-kafka-client in Storm 1.x allowed you to use Kafka&#39;s
own mechanism to manage which spout tasks were responsible for which
partitions. This mechanism was a poor fit for Storm, and was deprecated in
1.2.0. It has been <a
href="https://issues.apache.org/jira/browse/STORM-2542.">removed
entirely in 2.0</a></p>
+<p>Storm-kafka-client in Storm 1.x allowed you to use Kafka&#39;s
own mechanism to manage which spout tasks were responsible for which
partitions. This mechanism was a poor fit for Storm, and was deprecated in
1.2.0. It has been <a
href="https://issues.apache.org/jira/browse/STORM-2542">removed
entirely in 2.0</a>.</p>
<p>The storm-kafka-client Subscription interface has also been removed.
It offered too limited control over the subscription behavior. It has been
replaced with the TopicFilter and ManualPartitioner interfaces. Unless you were
using a custom Subscription implementation, this will likely not
-affect you. If you were using a custom Subscription, <a
href="https://github.com/apache/storm/blob/master/docs/storm-kafka-client.md#manual-partition-assigment-advanced">the
storm-kafka-client documentation describes how to customize
assignment</a>
-.</p>
+affect you. If you were using a custom Subscription, <a
href="https://github.com/apache/storm/blob/master/docs/storm-kafka-client.md#manual-partition-assigment-advanced">the
storm-kafka-client documentation describes how to customize
assignment</a>.</p>
<h3 id="other-kafka-highlights">Other Kafka
Highlights</h3>
<ul>
-<li>The KafkaBolt now allows you to <a
href="https://issues.apache.org/jira/browse/STORM-3175.">specify a
callback that will be called when a batch is written to
Kafka</a></li>
+<li>The KafkaBolt now allows you to <a
href="https://issues.apache.org/jira/browse/STORM-3175">specify a
callback that will be called when a batch is written to
Kafka</a>.</li>
<li>The FirstPollOffsetStrategy behavior has been made consistent
between the non-Trident and Trident spouts. It is now always the case that
EARLIEST/LATEST only take effect on topology redeploy, and not when a worker
restarts <a
href="https://issues.apache.org/jira/browse/STORM-2990">https://issues.apache.org/jira/browse/STORM-2990</a>.</li>
<li>Storm-kafka-client now has a transactional non-opaque Trident spout
<a
href="https://issues.apache.org/jira/browse/STORM-2974">https://issues.apache.org/jira/browse/STORM-2974</a>.</li>
<li>There are new example modules for storm-kafka-client. You can find
them <a
href="https://github.com/apache/storm/tree/master/examples/storm-kafka-client-examples">here</a>.</li>
@@ -69,6 +68,24 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<p>With the release of 2.0.0 the 1.0.x version line will no longer be
maintained. 1.0.x users are strongly encouraged to upgrade to a more recent
release.</p>
+<h2 id="move-to-java-8">Move to Java 8</h2>
+
+<p>Java 7 support has been dropped, and Storm 2.0.0 requires Java
8.</p>
+
+<h2
id="reorganization-of-storm-maven-artifacts">Reorganization of
Storm Maven artifacts</h2>
+
+<p>The storm-core artifact has <a
href="https://issues.apache.org/jira/browse/STORM-2441">been
split</a> into client and server-facing parts. Topology jars should
depend on the following artifact as of Storm 2.0.0:</p>
+<div class="highlight"><pre><code
class="language-"
data-lang="">&lt;groupId&gt;org.apache.storm&lt;/groupId&gt;
+&lt;artifactId&gt;storm-client&lt;/artifactId&gt;
+&lt;version&gt;2.0.0&lt;/version&gt;
+&lt;scope&gt;provided&lt;/scope&gt;
+</code></pre></div>
+<p>Projects using <code>LocalCluster</code> for testing will
additionally need to depend on the Storm server jar:</p>
+<div class="highlight"><pre><code
class="language-"
data-lang="">&lt;groupId&gt;org.apache.storm&lt;/groupId&gt;
+&lt;artifactId&gt;storm-server&lt;/artifactId&gt;
+&lt;version&gt;2.0.0&lt;/version&gt;
+&lt;scope&gt;test&lt;/scope&gt;
+</code></pre></div>
<h2 id="stay-tuned">Stay Tuned</h2>
<p>Keep an eye on the Apache Storm blog for additional posts by Storm
contributors for more in-depth discussions of new features in Storm 2.0.0
including:</p>
@@ -88,7 +105,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<p>Special thanks are due to all those who have contributed to Apache
Storm -- whether through direct code contributions, documentation, bug reports,
or helping other users on the mailing lists. Your efforts are much
appreciated.</p>
</description>
- <pubDate>Thu, 30 May 2019 00:00:00 -0400</pubDate>
+ <pubDate>Thu, 30 May 2019 00:00:00 +0200</pubDate>
<link>http://storm.apache.org/2019/05/30/storm200-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2019/05/30/storm200-released.html</guid>
@@ -159,7 +176,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<li>[<a
href="https://issues.apache.org/jira/browse/STORM-3005">STORM-3005</a>]
- [DRPC] LinearDRPCTopologyBuilder shouldn't be deprecated </li>
</ul>
</description>
- <pubDate>Mon, 04 Jun 2018 00:00:00 -0400</pubDate>
+ <pubDate>Mon, 04 Jun 2018 00:00:00 +0200</pubDate>
<link>http://storm.apache.org/2018/06/04/storm122-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2018/06/04/storm122-released.html</guid>
@@ -230,7 +247,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<p></body>
</html></p>
</description>
- <pubDate>Mon, 04 Jun 2018 00:00:00 -0400</pubDate>
+ <pubDate>Mon, 04 Jun 2018 00:00:00 +0200</pubDate>
<link>http://storm.apache.org/2018/06/04/storm113-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2018/06/04/storm113-released.html</guid>
@@ -265,7 +282,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<li>[<a
href="https://issues.apache.org/jira/browse/STORM-2841">STORM-2841</a>]
- testNoAcksIfFlushFails UT fails with NullPointerException</li>
</ul>
</description>
- <pubDate>Mon, 19 Feb 2018 00:00:00 -0500</pubDate>
+ <pubDate>Mon, 19 Feb 2018 00:00:00 +0100</pubDate>
<link>http://storm.apache.org/2018/02/19/storm121-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2018/02/19/storm121-released.html</guid>
@@ -490,7 +507,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<p></body>
</html></p>
</description>
- <pubDate>Thu, 15 Feb 2018 00:00:00 -0500</pubDate>
+ <pubDate>Thu, 15 Feb 2018 00:00:00 +0100</pubDate>
<link>http://storm.apache.org/2018/02/15/storm120-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2018/02/15/storm120-released.html</guid>
@@ -592,7 +609,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<p></body>
</html></p>
</description>
- <pubDate>Thu, 15 Feb 2018 00:00:00 -0500</pubDate>
+ <pubDate>Thu, 15 Feb 2018 00:00:00 +0100</pubDate>
<link>http://storm.apache.org/2018/02/15/storm112-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2018/02/15/storm112-released.html</guid>
@@ -658,7 +675,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<p></body>
</html></p>
</description>
- <pubDate>Wed, 14 Feb 2018 00:00:00 -0500</pubDate>
+ <pubDate>Wed, 14 Feb 2018 00:00:00 +0100</pubDate>
<link>http://storm.apache.org/2018/02/14/storm106-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2018/02/14/storm106-released.html</guid>
@@ -695,7 +712,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<li>[<a
href="https://issues.apache.org/jira/browse/STORM-2705">STORM-2705</a>]
- DRPCSpout sleeps twice when idle</li>
</ul>
</description>
- <pubDate>Fri, 15 Sep 2017 00:00:00 -0400</pubDate>
+ <pubDate>Fri, 15 Sep 2017 00:00:00 +0200</pubDate>
<link>http://storm.apache.org/2017/09/15/storm105-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2017/09/15/storm105-released.html</guid>
@@ -762,7 +779,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<li>STORM-2432: Storm-Kafka-Client Trident Spout Seeks Incorrect Offset
With UNCOMMITTED_LATEST Strategy</li>
</ul>
</description>
- <pubDate>Tue, 01 Aug 2017 00:00:00 -0400</pubDate>
+ <pubDate>Tue, 01 Aug 2017 00:00:00 +0200</pubDate>
<link>http://storm.apache.org/2017/08/01/storm111-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2017/08/01/storm111-released.html</guid>
@@ -813,7 +830,7 @@ affect you. If you were using a custom Subscription, <a
href="https://gi
<li>STORM-2350: Storm-HDFS&#39;s listFilesByModificationTime is
broken</li>
</ul>
</description>
- <pubDate>Fri, 28 Jul 2017 00:00:00 -0400</pubDate>
+ <pubDate>Fri, 28 Jul 2017 00:00:00 +0200</pubDate>
<link>http://storm.apache.org/2017/07/28/storm104-released.html</link>
<guid
isPermaLink="true">http://storm.apache.org/2017/07/28/storm104-released.html</guid>
diff --git a/content/releases.html b/content/releases.html
index 0dfd747..211be32 100644
--- a/content/releases.html
+++ b/content/releases.html
@@ -366,34 +366,6 @@
<hr>
- <a
href="http://github.com/apache/storm/tree/v0.10.0-beta1";>Apache Storm
0.10.0-beta1 on Github</a><br />
-
-
- <ul>
- <li><a
href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz";>apache-storm-0.10.0-beta1.tar.gz</a>
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.asc";>PGP</a>]
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.sha";>SHA512</a>]
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.md5";>MD5</a>]
- </li>
- <li><a
href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip";>apache-storm-0.10.0-beta1.zip</a>
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.asc";>PGP</a>]
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.sha";>SHA512</a>]
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.md5";>MD5</a>]
- </li>
- <li><a
href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz";>apache-storm-0.10.0-beta1-src.tar.gz</a>
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.asc";>PGP</a>]
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.sha";>SHA512</a>]
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.md5";>MD5</a>]
- </li>
- <li><a
href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip";>apache-storm-0.10.0-beta1-src.zip</a>
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.asc";>PGP</a>]
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.sha";>SHA512</a>]
- [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.md5";>MD5</a>]
- </li>
- </ul>
-
- <hr>
-
<a
href="http://github.com/apache/storm/tree/v0.10.0";>Apache Storm 0.10.0 on
Github</a><br />
@@ -422,6 +394,34 @@
<hr>
+ <a
href="http://github.com/apache/storm/tree/v0.10.0-beta1";>Apache Storm
0.10.0-beta1 on Github</a><br />
+
+
+ <ul>
+ <li><a
href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz";>apache-storm-0.10.0-beta1.tar.gz</a>
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.asc";>PGP</a>]
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.sha";>SHA512</a>]
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.md5";>MD5</a>]
+ </li>
+ <li><a
href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip";>apache-storm-0.10.0-beta1.zip</a>
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.asc";>PGP</a>]
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.sha";>SHA512</a>]
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.md5";>MD5</a>]
+ </li>
+ <li><a
href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz";>apache-storm-0.10.0-beta1-src.tar.gz</a>
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.asc";>PGP</a>]
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.sha";>SHA512</a>]
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.md5";>MD5</a>]
+ </li>
+ <li><a
href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip";>apache-storm-0.10.0-beta1-src.zip</a>
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.asc";>PGP</a>]
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.sha";>SHA512</a>]
+ [<a
href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.md5";>MD5</a>]
+ </li>
+ </ul>
+
+ <hr>
+
<a
href="http://github.com/apache/storm/tree/v0.9.6";>Apache Storm 0.9.6 on
Github</a><br />
diff --git a/content/releases/1.2.2/metrics_v2.html
b/content/releases/1.2.2/metrics_v2.html
index 94260aa..5f01744 100644
--- a/content/releases/1.2.2/metrics_v2.html
+++ b/content/releases/1.2.2/metrics_v2.html
@@ -210,7 +210,7 @@ be replaced with an underscore (<code>_</code>) character.
For example, the host
<ul>
<li>Console Reporter
(<code>org.apache.storm.metrics2.reporters.ConsoleStormReporter</code>):
Reports metrics to <code>System.out</code>.</li>
-<li>CSV Reporter
(<code>org.apache.storm.metrics2.reporters.CsvReporter</code>):
+<li>CSV Reporter
(<code>org.apache.storm.metrics2.reporters.CsvStormReporter</code>):
Reports metrics to a CSV file.</li>
<li>Ganglia Reporter
(<code>org.apache.storm.metrics2.reporters.GagliaStormReporter</code>):
Reports metrics to a <a href="http://ganglia.info";>Ganglia</a> server.</li>
diff --git a/content/releases/2.0.0-SNAPSHOT/metrics_v2.html
b/content/releases/2.0.0-SNAPSHOT/metrics_v2.html
index 2d32fcc..a588517 100644
--- a/content/releases/2.0.0-SNAPSHOT/metrics_v2.html
+++ b/content/releases/2.0.0-SNAPSHOT/metrics_v2.html
@@ -210,7 +210,7 @@ be replaced with an underscore (<code>_</code>) character.
For example, the host
<ul>
<li>Console Reporter
(<code>org.apache.storm.metrics2.reporters.ConsoleStormReporter</code>):
Reports metrics to <code>System.out</code>.</li>
-<li>CSV Reporter
(<code>org.apache.storm.metrics2.reporters.CsvReporter</code>):
+<li>CSV Reporter
(<code>org.apache.storm.metrics2.reporters.CsvStormReporter</code>):
Reports metrics to a CSV file.</li>
<li>Ganglia Reporter
(<code>org.apache.storm.metrics2.reporters.GagliaStormReporter</code>):
Reports metrics to a <a href="http://ganglia.info";>Ganglia</a> server.</li>
diff --git a/content/releases/current/metrics_v2.html
b/content/releases/current/metrics_v2.html
index 94260aa..5f01744 100644
--- a/content/releases/current/metrics_v2.html
+++ b/content/releases/current/metrics_v2.html
@@ -210,7 +210,7 @@ be replaced with an underscore (<code>_</code>) character.
For example, the host
<ul>
<li>Console Reporter
(<code>org.apache.storm.metrics2.reporters.ConsoleStormReporter</code>):
Reports metrics to <code>System.out</code>.</li>
-<li>CSV Reporter
(<code>org.apache.storm.metrics2.reporters.CsvReporter</code>):
+<li>CSV Reporter
(<code>org.apache.storm.metrics2.reporters.CsvStormReporter</code>):
Reports metrics to a CSV file.</li>
<li>Ganglia Reporter
(<code>org.apache.storm.metrics2.reporters.GagliaStormReporter</code>):
Reports metrics to a <a href="http://ganglia.info";>Ganglia</a> server.</li>
