You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by sr...@apache.org on 2018/05/15 15:21:01 UTC
[8/9] storm-site git commit: Rebuild site
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/STORM-UI-REST-API.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/STORM-UI-REST-API.html b/content/releases/1.0.6/STORM-UI-REST-API.html
index deb9bb0..3513378 100644
--- a/content/releases/1.0.6/STORM-UI-REST-API.html
+++ b/content/releases/1.0.6/STORM-UI-REST-API.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>The Storm UI daemon provides a REST API that allows you to interact with a Storm cluster, which includes retrieving
+<div class="documentation-content"><p>The Storm UI daemon provides a REST API that allows you to interact with a Storm cluster, which includes retrieving
metrics data and configuration information as well as management operations such as starting or stopping topologies.</p>
<h1 id="data-format">Data format</h1>
@@ -1857,7 +1857,7 @@ daemons.</p>
</span><span class="s2">"error"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Internal Server Error"</span><span class="p">,</span><span class="w">
</span><span class="s2">"errorMessage"</span><span class="p">:</span><span class="w"> </span><span class="s2">"java.lang.NullPointerException</span><span class="se">\n\t</span><span class="s2">at clojure.core$name.invoke(core.clj:1505)</span><span class="se">\n\t</span><span class="s2">at org.apache.storm.ui.core$component_page.invoke(core.clj:752)</span><span class="se">\n\t</span><span class="s2">at org.apache.storm.ui.core$fn__7766.invoke(core.clj:782)</span><span class="se">\n\t</span><span class="s2">at compojure.core$make_route$fn__5755.invoke(core.clj:93)</span><span class="se">\n\t</span><span class="s2">at compojure.core$if_route$fn__5743.invoke(core.clj:39)</span><span class="se">\n\t</span><span class="s2">at compojure.core$if_method$fn__5736.invoke(core.clj:24)</span><span class="se">\n\t</span><span class="s2">at compojure.core$routing$fn__5761.invoke(core.clj:106)</span><span class="se">\n\t</span><span class="s2">at clojure.core$some.invoke(core.clj:2443)</span><spa
n class="se">\n\t</span><span class="s2">at compojure.core$routing.doInvoke(core.clj:106)</span><span class="se">\n\t</span><span class="s2">at clojure.lang.RestFn.applyTo(RestFn.java:139)</span><span class="se">\n\t</span><span class="s2">at clojure.core$apply.invoke(core.clj:619)</span><span class="se">\n\t</span><span class="s2">at compojure.core$routes$fn__5765.invoke(core.clj:111)</span><span class="se">\n\t</span><span class="s2">at ring.middleware.reload$wrap_reload$fn__6880.invoke(reload.clj:14)</span><span class="se">\n\t</span><span class="s2">at org.apache.storm.ui.core$catch_errors$fn__7800.invoke(core.clj:836)</span><span class="se">\n\t</span><span class="s2">at ring.middleware.keyword_params$wrap_keyword_params$fn__6319.invoke(keyword_params.clj:27)</span><span class="se">\n\t</span><span class="s2">at ring.middleware.nested_params$wrap_nested_params$fn__6358.invoke(nested_params.clj:65)</span><span class="se">\n\t</span><span class="s2">at ring.middleware.params$wrap
_params$fn__6291.invoke(params.clj:55)</span><span class="se">\n\t</span><span class="s2">at ring.middleware.multipart_params$wrap_multipart_params$fn__6386.invoke(multipart_params.clj:103)</span><span class="se">\n\t</span><span class="s2">at ring.middleware.flash$wrap_flash$fn__6675.invoke(flash.clj:14)</span><span class="se">\n\t</span><span class="s2">at ring.middleware.session$wrap_session$fn__6664.invoke(session.clj:43)</span><span class="se">\n\t</span><span class="s2">at ring.middleware.cookies$wrap_cookies$fn__6595.invoke(cookies.clj:160)</span><span class="se">\n\t</span><span class="s2">at ring.adapter.jetty$proxy_handler$fn__6112.invoke(jetty.clj:16)</span><span class="se">\n\t</span><span class="s2">at ring.adapter.jetty.proxy$org.mortbay.jetty.handler.AbstractHandler$0.handle(Unknown Source)</span><span class="se">\n\t</span><span class="s2">at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)</span><span class="se">\n\t</span><span class="s2">at
org.mortbay.jetty.Server.handle(Server.java:326)</span><span class="se">\n\t</span><span class="s2">at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)</span><span class="se">\n\t</span><span class="s2">at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)</span><span class="se">\n\t</span><span class="s2">at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)</span><span class="se">\n\t</span><span class="s2">at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)</span><span class="se">\n\t</span><span class="s2">at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)</span><span class="se">\n\t</span><span class="s2">at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)</span><span class="se">\n\t</span><span class="s2">at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)</span><span class="se">\n</span><span class="s2">"</span><span
class="w">
</span><span class="p">}</span><span class="w">
-</span></code></pre></div>
+</span></code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Serialization-(prior-to-0.6.0).html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Serialization-(prior-to-0.6.0).html b/content/releases/1.0.6/Serialization-(prior-to-0.6.0).html
index e6da1a9..0c392ab 100644
--- a/content/releases/1.0.6/Serialization-(prior-to-0.6.0).html
+++ b/content/releases/1.0.6/Serialization-(prior-to-0.6.0).html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Tuples can be comprised of objects of any types. Since Storm is a distributed system, it needs to know how to serialize and deserialize objects when they're passed between tasks. By default Storm can serialize ints, shorts, longs, floats, doubles, bools, bytes, strings, and byte arrays, but if you want to use another type in your tuples, you'll need to implement a custom serializer.</p>
+<div class="documentation-content"><p>Tuples can be comprised of objects of any types. Since Storm is a distributed system, it needs to know how to serialize and deserialize objects when they're passed between tasks. By default Storm can serialize ints, shorts, longs, floats, doubles, bools, bytes, strings, and byte arrays, but if you want to use another type in your tuples, you'll need to implement a custom serializer.</p>
<h3 id="dynamic-typing">Dynamic typing</h3>
@@ -188,7 +188,7 @@
<p>Storm provides helpers for registering serializers in a topology config. The <a href="javadocs/backtype/storm/Config.html">Config</a> class has a method called <code>addSerialization</code> that takes in a serializer class to add to the config.</p>
<p>There's an advanced config called Config.TOPOLOGY_SKIP_MISSING_SERIALIZATIONS. If you set this to true, Storm will ignore any serializations that are registered but do not have their code available on the classpath. Otherwise, Storm will throw errors when it can't find a serialization. This is useful if you run many topologies on a cluster that each have different serializations, but you want to declare all the serializations across all topologies in the <code>storm.yaml</code> files.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Serialization.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Serialization.html b/content/releases/1.0.6/Serialization.html
index 4ea4822..f596ed9 100644
--- a/content/releases/1.0.6/Serialization.html
+++ b/content/releases/1.0.6/Serialization.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page is about how the serialization system in Storm works for versions 0.6.0 and onwards. Storm used a different serialization system prior to 0.6.0 which is documented on <a href="Serialization-(prior-to-0.6.0).html">Serialization (prior to 0.6.0)</a>. </p>
+<div class="documentation-content"><p>This page is about how the serialization system in Storm works for versions 0.6.0 and onwards. Storm used a different serialization system prior to 0.6.0 which is documented on <a href="Serialization-(prior-to-0.6.0).html">Serialization (prior to 0.6.0)</a>. </p>
<p>Tuples can be comprised of objects of any types. Since Storm is a distributed system, it needs to know how to serialize and deserialize objects when they're passed between tasks.</p>
@@ -200,7 +200,7 @@
<p>When a topology is submitted, a single set of serializations is chosen to be used by all components in the topology for sending messages. This is done by merging the component-specific serializer registrations with the regular set of serialization registrations. If two components define serializers for the same class, one of the serializers is chosen arbitrarily.</p>
<p>To force a serializer for a particular class if there's a conflict between two component-specific registrations, just define the serializer you want to use in the topology-specific configuration. The topology-specific configuration has precedence over component-specific configurations for serialization registrations.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Serializers.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Serializers.html b/content/releases/1.0.6/Serializers.html
index 218a67c..521f358 100644
--- a/content/releases/1.0.6/Serializers.html
+++ b/content/releases/1.0.6/Serializers.html
@@ -144,10 +144,10 @@
<p class="post-meta"></p>
-<ul>
+<div class="documentation-content"><ul>
<li><a href="https://github.com/rapportive-oss/storm-json">storm-json</a>: Simple JSON serializer for Storm</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Setting-up-a-Storm-cluster.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Setting-up-a-Storm-cluster.html b/content/releases/1.0.6/Setting-up-a-Storm-cluster.html
index 50ab855..fdf97e0 100644
--- a/content/releases/1.0.6/Setting-up-a-Storm-cluster.html
+++ b/content/releases/1.0.6/Setting-up-a-Storm-cluster.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page outlines the steps for getting a Storm cluster up and running. If you're on AWS, you should check out the <a href="https://github.com/nathanmarz/storm-deploy/wiki">storm-deploy</a> project. <a href="https://github.com/nathanmarz/storm-deploy/wiki">storm-deploy</a> completely automates the provisioning, configuration, and installation of Storm clusters on EC2. It also sets up Ganglia for you so you can monitor CPU, disk, and network usage.</p>
+<div class="documentation-content"><p>This page outlines the steps for getting a Storm cluster up and running. If you're on AWS, you should check out the <a href="https://github.com/nathanmarz/storm-deploy/wiki">storm-deploy</a> project. <a href="https://github.com/nathanmarz/storm-deploy/wiki">storm-deploy</a> completely automates the provisioning, configuration, and installation of Storm clusters on EC2. It also sets up Ganglia for you so you can monitor CPU, disk, and network usage.</p>
<p>If you run into difficulties with your Storm cluster, first check for a solution is in the <a href="Troubleshooting.html">Troubleshooting</a> page. Otherwise, email the mailing list.</p>
@@ -246,7 +246,7 @@ The time to allow any given healthcheck script to run before it is marked failed
</ol>
<p>As you can see, running the daemons is very straightforward. The daemons will log to the logs/ directory in wherever you extracted the Storm release.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Setting-up-development-environment.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Setting-up-development-environment.html b/content/releases/1.0.6/Setting-up-development-environment.html
index a369930..9abaecd 100644
--- a/content/releases/1.0.6/Setting-up-development-environment.html
+++ b/content/releases/1.0.6/Setting-up-development-environment.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page outlines what you need to do to get a Storm development environment set up. In summary, the steps are:</p>
+<div class="documentation-content"><p>This page outlines what you need to do to get a Storm development environment set up. In summary, the steps are:</p>
<ol>
<li>Download a <a href="..//downloads.html">Storm release</a> , unpack it, and put the unpacked <code>bin/</code> directory on your PATH</li>
@@ -171,7 +171,7 @@
<p>The previous step installed the <code>storm</code> client on your machine which is used to communicate with remote Storm clusters. Now all you have to do is tell the client which Storm cluster to talk to. To do this, all you have to do is put the host address of the master in the <code>~/.storm/storm.yaml</code> file. It should look something like this:</p>
<div class="highlight"><pre><code class="language-" data-lang="">nimbus.seeds: ["123.45.678.890"]
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Spout-implementations.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Spout-implementations.html b/content/releases/1.0.6/Spout-implementations.html
index c6ef895..7db2939 100644
--- a/content/releases/1.0.6/Spout-implementations.html
+++ b/content/releases/1.0.6/Spout-implementations.html
@@ -144,14 +144,14 @@
<p class="post-meta"></p>
-<ul>
+<div class="documentation-content"><ul>
<li><a href="https://github.com/nathanmarz/storm-kestrel">storm-kestrel</a>: Adapter to use Kestrel as a spout</li>
<li><a href="https://github.com/rapportive-oss/storm-amqp-spout">storm-amqp-spout</a>: Adapter to use AMQP source as a spout</li>
<li><a href="https://github.com/ptgoetz/storm-jms">storm-jms</a>: Adapter to use a JMS source as a spout</li>
<li><a href="https://github.com/sorenmacbeth/storm-redis-pubsub">storm-redis-pubsub</a>: A spout that subscribes to a Redis pubsub stream</li>
<li><a href="https://github.com/haitaoyao/storm-beanstalkd-spout">storm-beanstalkd-spout</a>: A spout that subscribes to a beanstalkd queue</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/State-checkpointing.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/State-checkpointing.html b/content/releases/1.0.6/State-checkpointing.html
index c429fe4..34ca603 100644
--- a/content/releases/1.0.6/State-checkpointing.html
+++ b/content/releases/1.0.6/State-checkpointing.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h1 id="state-support-in-core-storm">State support in core storm</h1>
+<div class="documentation-content"><h1 id="state-support-in-core-storm">State support in core storm</h1>
<p>Storm core has abstractions for bolts to save and retrieve the state of its operations. There is a default in-memory
based state implementation and also a Redis backed implementation that provides state persistence.</p>
@@ -302,7 +302,7 @@ The framework instantiates the state via the corresponding `StateProvider` imple
a `StateProvider` implementation which can load and return the state based on the namespace. Each state belongs to a unique namespace.
The namespace is typically unique per task so that each task can have its own state. The StateProvider and the corresponding
State implementation should be available in the class path of Storm (by placing them in the extlib directory).
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Storm-Scheduler.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Storm-Scheduler.html b/content/releases/1.0.6/Storm-Scheduler.html
index 39adc6f..b3871cd 100644
--- a/content/releases/1.0.6/Storm-Scheduler.html
+++ b/content/releases/1.0.6/Storm-Scheduler.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm now has 4 kinds of built-in schedulers: <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/scheduler/DefaultScheduler.clj">DefaultScheduler</a>, <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/scheduler/IsolationScheduler.clj">IsolationScheduler</a>, <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/jvm/org/apache/storm/scheduler/multitenant/MultitenantScheduler.java">MultitenantScheduler</a>, <a href="Resource_Aware_Scheduler_overview.html">ResourceAwareScheduler</a>. </p>
+<div class="documentation-content"><p>Storm now has 4 kinds of built-in schedulers: <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/scheduler/DefaultScheduler.clj">DefaultScheduler</a>, <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/scheduler/IsolationScheduler.clj">IsolationScheduler</a>, <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/jvm/org/apache/storm/scheduler/multitenant/MultitenantScheduler.java">MultitenantScheduler</a>, <a href="Resource_Aware_Scheduler_overview.html">ResourceAwareScheduler</a>. </p>
<h2 id="pluggable-scheduler">Pluggable scheduler</h2>
@@ -163,7 +163,7 @@
<p>Any topologies submitted to the cluster not listed there will not be isolated. Note that there is no way for a user of Storm to affect their isolation settings – this is only allowed by the administrator of the cluster (this is very much intentional).</p>
<p>The isolation scheduler solves the multi-tenancy problem – avoiding resource contention between topologies – by providing full isolation between topologies. The intention is that "productionized" topologies should be listed in the isolation config, and test or in-development topologies should not. The remaining machines on the cluster serve the dual role of failover for isolated topologies and for running the non-isolated topologies.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Storm-multi-language-protocol-(versions-0.7.0-and-below).html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Storm-multi-language-protocol-(versions-0.7.0-and-below).html b/content/releases/1.0.6/Storm-multi-language-protocol-(versions-0.7.0-and-below).html
index 7a40d96..b0e9805 100644
--- a/content/releases/1.0.6/Storm-multi-language-protocol-(versions-0.7.0-and-below).html
+++ b/content/releases/1.0.6/Storm-multi-language-protocol-(versions-0.7.0-and-below).html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page explains the multilang protocol for versions 0.7.0 and below. The protocol changed in version 0.7.1.</p>
+<div class="documentation-content"><p>This page explains the multilang protocol for versions 0.7.0 and below. The protocol changed in version 0.7.1.</p>
<h1 id="storm-multi-language-protocol">Storm Multi-Language Protocol</h1>
@@ -253,7 +253,7 @@ file lets the supervisor know the PID so it can shutdown the process later on.</
<p>Note: This command is not JSON encoded, it is sent as a simple string.</p>
<p>This lets the parent bolt know that the script has finished processing and is ready for another tuple.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Structure-of-the-codebase.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Structure-of-the-codebase.html b/content/releases/1.0.6/Structure-of-the-codebase.html
index c749f0b..f690c84 100644
--- a/content/releases/1.0.6/Structure-of-the-codebase.html
+++ b/content/releases/1.0.6/Structure-of-the-codebase.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>There are three distinct layers to Storm's codebase.</p>
+<div class="documentation-content"><p>There are three distinct layers to Storm's codebase.</p>
<p>First, Storm was designed from the very beginning to be compatible with multiple languages. Nimbus is a Thrift service and topologies are defined as Thrift structures. The usage of Thrift allows Storm to be used from any language.</p>
@@ -287,7 +287,7 @@
<p><a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/util.clj">org.apache.storm.util</a>: Contains generic utility functions used throughout the code base.</p>
<p><a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/zookeeper.clj">org.apache.storm.zookeeper</a>: Clojure wrapper around the Zookeeper API and implements some "high-level" stuff like "mkdirs" and "delete-recursive".</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Support-for-non-java-languages.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Support-for-non-java-languages.html b/content/releases/1.0.6/Support-for-non-java-languages.html
index 16efdb7..486ed89 100644
--- a/content/releases/1.0.6/Support-for-non-java-languages.html
+++ b/content/releases/1.0.6/Support-for-non-java-languages.html
@@ -144,13 +144,13 @@
<p class="post-meta"></p>
-<ul>
+<div class="documentation-content"><ul>
<li><a href="https://github.com/velvia/ScalaStorm">Scala DSL</a></li>
<li><a href="https://github.com/colinsurprenant/storm-jruby">JRuby DSL</a></li>
<li><a href="Clojure-DSL.html">Clojure DSL</a></li>
<li><a href="https://github.com/gphat/io-storm">io-storm</a>: Perl multilang adapter</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Transactional-topologies.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Transactional-topologies.html b/content/releases/1.0.6/Transactional-topologies.html
index 3d61ef4..d0b9dae 100644
--- a/content/releases/1.0.6/Transactional-topologies.html
+++ b/content/releases/1.0.6/Transactional-topologies.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p><strong>NOTE</strong>: Transactional topologies have been deprecated -- use the <a href="Trident-tutorial.html">Trident</a> framework instead.</p>
+<div class="documentation-content"><p><strong>NOTE</strong>: Transactional topologies have been deprecated -- use the <a href="Trident-tutorial.html">Trident</a> framework instead.</p>
<hr>
@@ -510,7 +510,7 @@
<li>so it can't call finishbatch until it's received all tuples from all subscribed components AND its received the commit stream tuple (for committers). this ensures that it can't prematurely call finishBatch</li>
</ul></li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Trident-API-Overview.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Trident-API-Overview.html b/content/releases/1.0.6/Trident-API-Overview.html
index 40538ad..a787d91 100644
--- a/content/releases/1.0.6/Trident-API-Overview.html
+++ b/content/releases/1.0.6/Trident-API-Overview.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>The core data model in Trident is the "Stream", processed as a series of batches. A stream is partitioned among the nodes in the cluster, and operations applied to a stream are applied in parallel across each partition.</p>
+<div class="documentation-content"><p>The core data model in Trident is the "Stream", processed as a series of batches. A stream is partitioned among the nodes in the cluster, and operations applied to a stream are applied in parallel across each partition.</p>
<p>There are five kinds of operations in Trident:</p>
@@ -663,7 +663,7 @@ Partition 2:
<p>You might be wondering – how do you do something like a "windowed join", where tuples from one side of the join are joined against the last hour of tuples from the other side of the join.</p>
<p>To do this, you would make use of partitionPersist and stateQuery. The last hour of tuples from one side of the join would be stored and rotated in a source of state, keyed by the join field. Then the stateQuery would do lookups by the join field to perform the "join".</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Trident-RAS-API.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Trident-RAS-API.html b/content/releases/1.0.6/Trident-RAS-API.html
index c5f45b4..ca87add 100644
--- a/content/releases/1.0.6/Trident-RAS-API.html
+++ b/content/releases/1.0.6/Trident-RAS-API.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h2 id="trident-ras-api">Trident RAS API</h2>
+<div class="documentation-content"><h2 id="trident-ras-api">Trident RAS API</h2>
<p>The Trident RAS (Resource Aware Scheduler) API provides a mechanism to allow users to specify the resource consumption of a Trident topology. The API looks exactly like the base RAS API, only it is called on Trident Streams instead of Bolts and Spouts.</p>
@@ -192,7 +192,7 @@ Operations that are combined by Trident into single Bolts will have their resour
<p>Resource declarations may be called after any operation. The operations without explicit resources will get the defaults. If you choose to set resources for only some operations, defaults must be declared, or topology submission will fail.
Resource declarations have the same <em>boundaries</em> as parallelism hints. They don't cross any groupings, shufflings, or any other kind of repartitioning.
Resources are declared per operation, but get combined within boundaries.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Trident-spouts.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Trident-spouts.html b/content/releases/1.0.6/Trident-spouts.html
index efbcaed..2ab8611 100644
--- a/content/releases/1.0.6/Trident-spouts.html
+++ b/content/releases/1.0.6/Trident-spouts.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h1 id="trident-spouts">Trident spouts</h1>
+<div class="documentation-content"><h1 id="trident-spouts">Trident spouts</h1>
<p>Like in the vanilla Storm API, spouts are the source of streams in a Trident topology. On top of the vanilla Storm spouts, Trident exposes additional APIs for more sophisticated spouts.</p>
@@ -182,7 +182,7 @@
</ol>
<p>And, like mentioned in the beginning of this tutorial, you can use regular IRichSpout's as well.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Trident-state.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Trident-state.html b/content/releases/1.0.6/Trident-state.html
index bbb776d..04f5c70 100644
--- a/content/releases/1.0.6/Trident-state.html
+++ b/content/releases/1.0.6/Trident-state.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Trident has first-class abstractions for reading from and writing to stateful sources. The state can either be internal to the topology – e.g., kept in-memory and backed by HDFS – or externally stored in a database like Memcached or Cassandra. There's no difference in the Trident API for either case.</p>
+<div class="documentation-content"><p>Trident has first-class abstractions for reading from and writing to stateful sources. The state can either be internal to the topology – e.g., kept in-memory and backed by HDFS – or externally stored in a database like Memcached or Cassandra. There's no difference in the Trident API for either case.</p>
<p>Trident manages state in a fault-tolerant way so that state updates are idempotent in the face of retries and failures. This lets you reason about Trident topologies as if each message were processed exactly-once.</p>
@@ -413,7 +413,7 @@ apple => [count=10, txid=2]
<p>Finally, Trident provides the <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/jvm/org/apache/storm/trident/state/map/SnapshottableMap.java">SnapshottableMap</a> class that turns a MapState into a Snapshottable object, by storing global aggregations into a fixed key.</p>
<p>Take a look at the implementation of <a href="https://github.com/nathanmarz/trident-memcached/blob/master/src/jvm/trident/memcached/MemcachedState.java">MemcachedState</a> to see how all these utilities can be put together to make a high performance MapState implementation. MemcachedState allows you to choose between opaque transactional, transactional, and non-transactional semantics.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Trident-tutorial.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Trident-tutorial.html b/content/releases/1.0.6/Trident-tutorial.html
index ce93374..7654723 100644
--- a/content/releases/1.0.6/Trident-tutorial.html
+++ b/content/releases/1.0.6/Trident-tutorial.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Trident is a high-level abstraction for doing realtime computing on top of Storm. It allows you to seamlessly intermix high throughput (millions of messages per second), stateful stream processing with low latency distributed querying. If you're familiar with high level batch processing tools like Pig or Cascading, the concepts of Trident will be very familiar – Trident has joins, aggregations, grouping, functions, and filters. In addition to these, Trident adds primitives for doing stateful, incremental processing on top of any database or persistence store. Trident has consistent, exactly-once semantics, so it is easy to reason about Trident topologies.</p>
+<div class="documentation-content"><p>Trident is a high-level abstraction for doing realtime computing on top of Storm. It allows you to seamlessly intermix high throughput (millions of messages per second), stateful stream processing with low latency distributed querying. If you're familiar with high level batch processing tools like Pig or Cascading, the concepts of Trident will be very familiar – Trident has joins, aggregations, grouping, functions, and filters. In addition to these, Trident adds primitives for doing stateful, incremental processing on top of any database or persistence store. Trident has consistent, exactly-once semantics, so it is easy to reason about Trident topologies.</p>
<h2 id="illustrative-example">Illustrative example</h2>
@@ -356,7 +356,7 @@
<h2 id="conclusion">Conclusion</h2>
<p>Trident makes realtime computation elegant. You've seen how high throughput stream processing, state manipulation, and low-latency querying can be seamlessly intermixed via Trident's API. Trident lets you express your realtime computations in a natural way while still getting maximal performance.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Troubleshooting.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Troubleshooting.html b/content/releases/1.0.6/Troubleshooting.html
index 81b6c37..07d91cd 100644
--- a/content/releases/1.0.6/Troubleshooting.html
+++ b/content/releases/1.0.6/Troubleshooting.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page lists issues people have run into when using Storm along with their solutions.</p>
+<div class="documentation-content"><p>This page lists issues people have run into when using Storm along with their solutions.</p>
<h3 id="worker-processes-are-crashing-on-startup-with-no-stack-trace">Worker processes are crashing on startup with no stack trace</h3>
@@ -279,7 +279,7 @@ Caused by: java.util.ConcurrentModificationException
<ul>
<li>This means that you're emitting a mutable object as an output tuple. Everything you emit into the output collector must be immutable. What's happening is that your bolt is modifying the object while it is being serialized to be sent over the network.</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Tutorial.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Tutorial.html b/content/releases/1.0.6/Tutorial.html
index 1c886c4..0ef8b3d 100644
--- a/content/releases/1.0.6/Tutorial.html
+++ b/content/releases/1.0.6/Tutorial.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>In this tutorial, you'll learn how to create Storm topologies and deploy them to a Storm cluster. Java will be the main language used, but a few examples will use Python to illustrate Storm's multi-language capabilities.</p>
+<div class="documentation-content"><p>In this tutorial, you'll learn how to create Storm topologies and deploy them to a Storm cluster. Java will be the main language used, but a few examples will use Python to illustrate Storm's multi-language capabilities.</p>
<h2 id="preliminaries">Preliminaries</h2>
@@ -428,7 +428,7 @@
<h2 id="conclusion">Conclusion</h2>
<p>This tutorial gave a broad overview of developing, testing, and deploying Storm topologies. The rest of the documentation dives deeper into all the aspects of using Storm.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Understanding-the-parallelism-of-a-Storm-topology.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Understanding-the-parallelism-of-a-Storm-topology.html b/content/releases/1.0.6/Understanding-the-parallelism-of-a-Storm-topology.html
index da8b94a..9eef7a9 100644
--- a/content/releases/1.0.6/Understanding-the-parallelism-of-a-Storm-topology.html
+++ b/content/releases/1.0.6/Understanding-the-parallelism-of-a-Storm-topology.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h2 id="what-makes-a-running-topology-worker-processes-executors-and-tasks">What makes a running topology: worker processes, executors and tasks</h2>
+<div class="documentation-content"><h2 id="what-makes-a-running-topology-worker-processes-executors-and-tasks">What makes a running topology: worker processes, executors and tasks</h2>
<p>Storm distinguishes between the following three main entities that are used to actually run a topology in a Storm cluster:</p>
@@ -274,7 +274,7 @@ $ storm rebalance mytopology -n 5 -e blue-spout=3 -e yellow-bolt=10
<li><a href="Tutorial.html">Tutorial</a></li>
<li><a href="javadocs/">Storm API documentation</a>, most notably the class <code>Config</code></li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Using-non-JVM-languages-with-Storm.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Using-non-JVM-languages-with-Storm.html b/content/releases/1.0.6/Using-non-JVM-languages-with-Storm.html
index 07d621d..9b8259c 100644
--- a/content/releases/1.0.6/Using-non-JVM-languages-with-Storm.html
+++ b/content/releases/1.0.6/Using-non-JVM-languages-with-Storm.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<ul>
+<div class="documentation-content"><ul>
<li>two pieces: creating topologies and implementing spouts and bolts in other languages</li>
<li>creating topologies in another language is easy since topologies are just thrift structures (link to storm.thrift)</li>
<li>implementing spouts and bolts in another language is called a "multilang components" or "shelling"
@@ -198,7 +198,7 @@
<p>Then you can connect to Nimbus using the Thrift API and submit the topology, passing {uploaded-jar-location} into the submitTopology method. For reference, here's the submitTopology definition:</p>
<div class="highlight"><pre><code class="language-" data-lang="">void submitTopology(1: string name, 2: string uploadedJarLocation, 3: string jsonConf, 4: StormTopology topology)
throws (1: AlreadyAliveException e, 2: InvalidTopologyException ite);
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Windowing.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Windowing.html b/content/releases/1.0.6/Windowing.html
index 4354e21..3a1e98e 100644
--- a/content/releases/1.0.6/Windowing.html
+++ b/content/releases/1.0.6/Windowing.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm core has support for processing a group of tuples that falls within a window. Windows are specified with the
+<div class="documentation-content"><p>Storm core has support for processing a group of tuples that falls within a window. Windows are specified with the
following two parameters,</p>
<ol>
@@ -359,7 +359,7 @@ tuples can be received within the timeout period.</p>
<p>An example toplogy <code>SlidingWindowTopology</code> shows how to use the apis to compute a sliding window sum and a tumbling window
average.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/distcache-blobstore.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/distcache-blobstore.html b/content/releases/1.0.6/distcache-blobstore.html
index 043c62c..5cf40cc 100644
--- a/content/releases/1.0.6/distcache-blobstore.html
+++ b/content/releases/1.0.6/distcache-blobstore.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h1 id="storm-distributed-cache-api">Storm Distributed Cache API</h1>
+<div class="documentation-content"><h1 id="storm-distributed-cache-api">Storm Distributed Cache API</h1>
<p>The distributed cache feature in storm is used to efficiently distribute files
(or blobs, which is the equivalent terminology for a file in the distributed
@@ -799,7 +799,7 @@ struct BeginDownloadResult {
2: required string session;
3: optional i64 data_size;
}
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/dynamic-log-level-settings.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/dynamic-log-level-settings.html b/content/releases/1.0.6/dynamic-log-level-settings.html
index 2fe8576..240b6a6 100644
--- a/content/releases/1.0.6/dynamic-log-level-settings.html
+++ b/content/releases/1.0.6/dynamic-log-level-settings.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>We have added the ability to set log level settings for a running topology using the Storm UI and the Storm CLI. </p>
+<div class="documentation-content"><p>We have added the ability to set log level settings for a running topology using the Storm UI and the Storm CLI. </p>
<p>The log level settings apply the same way as you'd expect from log4j, as all we are doing is telling log4j to set the level of the logger you provide. If you set the log level of a parent logger, the children loggers start using that level (unless the children have a more restrictive level already). A timeout can optionally be provided (except for DEBUG mode, where it’s required in the UI), if workers should reset log levels automatically.</p>
@@ -179,7 +179,7 @@
<p><code>./bin/storm set_log_level my_topology -r ROOT</code></p>
<p>Clears the ROOT logger dynamic log level, resetting it to its original value.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/dynamic-worker-profiling.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/dynamic-worker-profiling.html b/content/releases/1.0.6/dynamic-worker-profiling.html
index 17a2b70..294706c 100644
--- a/content/releases/1.0.6/dynamic-worker-profiling.html
+++ b/content/releases/1.0.6/dynamic-worker-profiling.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>In multi-tenant mode, storm launches long-running JVMs across cluster without sudo access to user. Self-serving of Java heap-dumps, jstacks and java profiling of these JVMs would improve users' ability to analyze and debug issues when monitoring it actively.</p>
+<div class="documentation-content"><p>In multi-tenant mode, storm launches long-running JVMs across cluster without sudo access to user. Self-serving of Java heap-dumps, jstacks and java profiling of these JVMs would improve users' ability to analyze and debug issues when monitoring it actively.</p>
<p>The storm dynamic profiler lets you dynamically take heap-dumps, jprofile or jstack for a worker jvm running on stock cluster. It let user download these dumps from the browser and use your favorite tools to analyze it The UI component page provides list workers for the component and action buttons. The logviewer lets you download the dumps generated by these logs. Please see the screenshots for more information.</p>
@@ -171,7 +171,7 @@
<h2 id="configuration">Configuration</h2>
<p>The "worker.profiler.command" can be configured to point to specific pluggable profiler, heapdump commands. The "worker.profiler.enabled" can be disabled if plugin is not available or jdk does not support Jprofile flight recording so that worker JVM options will not have "worker.profiler.childopts". To use different profiler plugin, you can change these configuration.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/flux.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/flux.html b/content/releases/1.0.6/flux.html
index 2055517..01f1d66 100644
--- a/content/releases/1.0.6/flux.html
+++ b/content/releases/1.0.6/flux.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>A framework for creating and deploying Apache Storm streaming computations with less friction.</p>
+<div class="documentation-content"><p>A framework for creating and deploying Apache Storm streaming computations with less friction.</p>
<h2 id="definition">Definition</h2>
@@ -908,7 +908,7 @@ same file. Includes may be either files, or classpath resources.</p>
<span class="na">className</span><span class="pi">:</span> <span class="s2">"</span><span class="s">org.apache.storm.flux.test.TridentTopologySource"</span>
<span class="c1"># Flux will look for "getTopology", this will override that.</span>
<span class="na">methodName</span><span class="pi">:</span> <span class="s2">"</span><span class="s">getTopologyWithDifferentMethodName"</span>
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/index.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/index.html b/content/releases/1.0.6/index.html
index e9aa523..bf2ad00 100644
--- a/content/releases/1.0.6/index.html
+++ b/content/releases/1.0.6/index.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<blockquote>
+<div class="documentation-content"><blockquote>
<h4 id="note">NOTE</h4>
<p>In the latest version, the class packages have been changed from "backtype.storm" to "org.apache.storm" so the topology code compiled with older version won't run on the Storm 1.0.0 just like that. Backward compatibility is available through following configuration </p>
@@ -256,7 +256,7 @@
<li><a href="Multilang-protocol.html">Multilang protocol</a> (how to provide support for another language)</li>
<li><a href="Implementation-docs.html">Implementation docs</a></li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/nimbus-ha-design.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/nimbus-ha-design.html b/content/releases/1.0.6/nimbus-ha-design.html
index 71e206d..57cde81 100644
--- a/content/releases/1.0.6/nimbus-ha-design.html
+++ b/content/releases/1.0.6/nimbus-ha-design.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h2 id="problem-statement">Problem Statement:</h2>
+<div class="documentation-content"><h2 id="problem-statement">Problem Statement:</h2>
<p>Currently the storm master aka nimbus, is a process that runs on a single machine under supervision. In most cases the
nimbus failure is transient and it is restarted by the supervisor. However sometimes when disks fail and networks
@@ -361,7 +361,7 @@ The default is 60 seconds, a value of -1 indicates to wait for ever.
<p>Note: Even though all nimbus hosts have watchers on zookeeper to be notified immediately as soon as a new topology is available for code
download, the callback pretty much never results in code download. In practice we have observed that the desired replication is only achieved once the background-thread runs.
So you should expect your topology submission time to be somewhere between 0 to (2 * nimbus.code.sync.freq.secs) for any nimbus.min.replication.count > 1.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-cassandra.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-cassandra.html b/content/releases/1.0.6/storm-cassandra.html
index 1d6885f..2eff1fb 100644
--- a/content/releases/1.0.6/storm-cassandra.html
+++ b/content/releases/1.0.6/storm-cassandra.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h3 id="bolt-api-implementation-for-apache-cassandra">Bolt API implementation for Apache Cassandra</h3>
+<div class="documentation-content"><h3 id="bolt-api-implementation-for-apache-cassandra">Bolt API implementation for Apache Cassandra</h3>
<p>This library provides core storm bolt on top of Apache Cassandra.
Provides simple DSL to map storm <em>Tuple</em> to Cassandra Query Language <em>Statement</em>.</p>
@@ -412,7 +412,7 @@ under the License.</p>
<li>Sriharha Chintalapani (<a href="mailto:sriharsha@apache.org">sriharsha@apache.org</a>)</li>
<li>P. Taylor Goetz (<a href="mailto:ptgoetz@apache.org">ptgoetz@apache.org</a>)</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-elasticsearch.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-elasticsearch.html b/content/releases/1.0.6/storm-elasticsearch.html
index a0e6a13..3356497 100644
--- a/content/releases/1.0.6/storm-elasticsearch.html
+++ b/content/releases/1.0.6/storm-elasticsearch.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h1 id="storm-elasticsearch-bolt-trident-state">Storm Elasticsearch Bolt & Trident State</h1>
+<div class="documentation-content"><h1 id="storm-elasticsearch-bolt-trident-state">Storm Elasticsearch Bolt & Trident State</h1>
<p>EsIndexBolt, EsPercolateBolt and EsState allows users to stream data from storm into Elasticsearch directly.
For detailed description, please refer to the following.</p>
@@ -245,7 +245,7 @@ You can refer implementation of DefaultEsTupleMapper to see how to implement you
<li>Sriharsha Chintalapani (<a href="https://github.com/harshach">@harshach</a>)</li>
<li>Jungtaek Lim (<a href="https://github.com/HeartSaVioR">@HeartSaVioR</a>)</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-eventhubs.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-eventhubs.html b/content/releases/1.0.6/storm-eventhubs.html
index 9015298..aed231e 100644
--- a/content/releases/1.0.6/storm-eventhubs.html
+++ b/content/releases/1.0.6/storm-eventhubs.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm spout and bolt implementation for Microsoft Azure Eventhubs</p>
+<div class="documentation-content"><p>Storm spout and bolt implementation for Microsoft Azure Eventhubs</p>
<h3 id="build">build</h3>
<div class="highlight"><pre><code class="language-" data-lang="">mvn clean package
@@ -178,7 +178,7 @@ If you want to send messages to all partitions, use "-1" as partitionI
<h3 id="windows-azure-eventhubs">Windows Azure Eventhubs</h3>
<div class="highlight"><pre><code class="language-" data-lang="">http://azure.microsoft.com/en-us/services/event-hubs/
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-hbase.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-hbase.html b/content/releases/1.0.6/storm-hbase.html
index 11e5e2d..d2a650e 100644
--- a/content/releases/1.0.6/storm-hbase.html
+++ b/content/releases/1.0.6/storm-hbase.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm/Trident integration for <a href="https://hbase.apache.org">Apache HBase</a></p>
+<div class="documentation-content"><p>Storm/Trident integration for <a href="https://hbase.apache.org">Apache HBase</a></p>
<h2 id="usage">Usage</h2>
@@ -359,7 +359,7 @@ Word: 'watermelon', Count: 6806
<span class="o">}</span>
<span class="o">}</span>
<span class="o">}</span>
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-hdfs.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-hdfs.html b/content/releases/1.0.6/storm-hdfs.html
index 9375660..47bbca2 100644
--- a/content/releases/1.0.6/storm-hdfs.html
+++ b/content/releases/1.0.6/storm-hdfs.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm components for interacting with HDFS file systems</p>
+<div class="documentation-content"><p>Storm components for interacting with HDFS file systems</p>
<h2 id="usage">Usage</h2>
@@ -460,7 +460,7 @@ hdfs.kerberos.principal: "<a href="mailto:user@EXAMPLE.com">user@EXAMPLE.co
<p>On worker hosts the bolt/trident-state code will use the keytab file with principal provided in the config to authenticate with
Namenode. This method is little dangerous as you need to ensure all workers have the keytab file at the same location and you need
to remember this as you bring up new hosts in the cluster.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-hive.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-hive.html b/content/releases/1.0.6/storm-hive.html
index c96ca92..2fe563b 100644
--- a/content/releases/1.0.6/storm-hive.html
+++ b/content/releases/1.0.6/storm-hive.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Hive offers streaming API that allows data to be written continuously into Hive. The incoming data
+<div class="documentation-content"><p>Hive offers streaming API that allows data to be written continuously into Hive. The incoming data
can be continuously committed in small batches of records into existing Hive partition or table. Once the data
is committed its immediately visible to all hive queries. More info on Hive Streaming API
<a href="https://cwiki.apache.org/confluence/display/Hive/Streaming+Data+Ingest">https://cwiki.apache.org/confluence/display/Hive/Streaming+Data+Ingest</a></p>
@@ -303,7 +303,7 @@ User should make sure that Tuple field names are matched to the table column nam
<span class="n">StateFactory</span> <span class="n">factory</span> <span class="o">=</span> <span class="k">new</span> <span class="n">HiveStateFactory</span><span class="o">().</span><span class="na">withOptions</span><span class="o">(</span><span class="n">hiveOptions</span><span class="o">);</span>
<span class="n">TridentState</span> <span class="n">state</span> <span class="o">=</span> <span class="n">stream</span><span class="o">.</span><span class="na">partitionPersist</span><span class="o">(</span><span class="n">factory</span><span class="o">,</span> <span class="n">hiveFields</span><span class="o">,</span> <span class="k">new</span> <span class="n">HiveUpdater</span><span class="o">(),</span> <span class="k">new</span> <span class="n">Fields</span><span class="o">());</span>
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-jdbc.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-jdbc.html b/content/releases/1.0.6/storm-jdbc.html
index ccd55a9..72c0c3e 100644
--- a/content/releases/1.0.6/storm-jdbc.html
+++ b/content/releases/1.0.6/storm-jdbc.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm/Trident integration for JDBC. This package includes the core bolts and trident states that allows a storm topology
+<div class="documentation-content"><p>Storm/Trident integration for JDBC. This package includes the core bolts and trident states that allows a storm topology
to either insert storm tuples in a database table or to execute select queries against a database and enrich tuples
in a storm topology.</p>
@@ -403,7 +403,7 @@ storm jar ~/repo/incubator-storm/external/storm-jdbc/target/storm-jdbc-0.10.0-SN
<div class="highlight"><pre><code class="language-" data-lang="">select * from user;
</code></pre></div>
<p>For trident you can view <code>org.apache.storm.jdbc.topology.UserPersistanceTridentTopology</code>.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-jms-example.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-jms-example.html b/content/releases/1.0.6/storm-jms-example.html
index be6ad5b..7b88bd6 100644
--- a/content/releases/1.0.6/storm-jms-example.html
+++ b/content/releases/1.0.6/storm-jms-example.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h2 id="example-storm-jms-topology">Example Storm JMS Topology</h2>
+<div class="documentation-content"><h2 id="example-storm-jms-topology">Example Storm JMS Topology</h2>
<p>The storm-jms source code contains an example project (in the "examples" directory)
builds a multi-bolt/multi-spout topology (depicted below) that uses the JMS Spout and JMS Bolt components.</p>
@@ -248,7 +248,7 @@ DEBUG (backtype.storm.contrib.jms.example.GenericBolt:75) - [ANOTHER_BOLT] ACKin
DEBUG (backtype.storm.contrib.jms.spout.JmsSpout:251) - JMS Message acked: ID:budreau.home-60117-1321735025796-0:0:1:1:1
</code></pre></div>
<p>The topology will run for 2 minutes, then gracefully shut down.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-jms-spring.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-jms-spring.html b/content/releases/1.0.6/storm-jms-spring.html
index 878df7a..d5938b0 100644
--- a/content/releases/1.0.6/storm-jms-spring.html
+++ b/content/releases/1.0.6/storm-jms-spring.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h3 id="connecting-to-jms-using-springs-jms-support">Connecting to JMS Using Spring's JMS Support</h3>
+<div class="documentation-content"><h3 id="connecting-to-jms-using-springs-jms-support">Connecting to JMS Using Spring's JMS Support</h3>
<p>Create a Spring applicationContext.xml file that defines one or more destination (topic/queue) beans, as well as a connecton factory.</p>
<div class="highlight"><pre><code class="language-" data-lang=""><span class="cp"><?xml version="1.0" encoding="UTF-8"?></span>
@@ -163,7 +163,7 @@
<span class="na">brokerURL=</span><span class="s">"tcp://localhost:61616"</span> <span class="nt">/></span>
<span class="nt"></beans></span>
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-jms.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-jms.html b/content/releases/1.0.6/storm-jms.html
index 1dc4c80..669f321 100644
--- a/content/releases/1.0.6/storm-jms.html
+++ b/content/releases/1.0.6/storm-jms.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h2 id="about-storm-jms">About Storm JMS</h2>
+<div class="documentation-content"><h2 id="about-storm-jms">About Storm JMS</h2>
<p>Storm JMS is a generic framework for integrating JMS messaging within the Storm framework.</p>
@@ -169,7 +169,7 @@
<p><a href="storm-jms-example.html">Example Topology</a></p>
<p><a href="storm-jms-spring.html">Using Spring JMS</a></p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-kafka-client.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-kafka-client.html b/content/releases/1.0.6/storm-kafka-client.html
index dbfa210..23c386a 100644
--- a/content/releases/1.0.6/storm-kafka-client.html
+++ b/content/releases/1.0.6/storm-kafka-client.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h1 id="storm-apache-kafka-integration-using-the-kafka-client-jar">Storm Apache Kafka integration using the kafka-client jar</h1>
+<div class="documentation-content"><h1 id="storm-apache-kafka-integration-using-the-kafka-client-jar">Storm Apache Kafka integration using the kafka-client jar</h1>
<p>This includes the new Apache Kafka consumer API.</p>
@@ -476,7 +476,7 @@ or enabling backpressure with Config.TOPOLOGY_MAX_SPOUT_PENDING.</p>
<span class="o">.</span><span class="na">setTupleTrackingEnforced</span><span class="o">(</span><span class="kc">true</span><span class="o">)</span>
</code></pre></div>
<p>Note: This setting has no effect with AT_LEAST_ONCE processing guarantee, where tuple tracking is required and therefore always enabled.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-kafka.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-kafka.html b/content/releases/1.0.6/storm-kafka.html
index dfc2335..5bdc618 100644
--- a/content/releases/1.0.6/storm-kafka.html
+++ b/content/releases/1.0.6/storm-kafka.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Provides core Storm and Trident spout implementations for consuming data from Apache Kafka 0.8.x.</p>
+<div class="documentation-content"><p>Provides core Storm and Trident spout implementations for consuming data from Apache Kafka 0.8.x.</p>
<h2 id="spouts">Spouts</h2>
@@ -493,7 +493,7 @@ For the bolt :
<span class="n">Config</span> <span class="n">conf</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Config</span><span class="o">();</span>
<span class="n">StormSubmitter</span><span class="o">.</span><span class="na">submitTopology</span><span class="o">(</span><span class="s">"kafkaTridentTest"</span><span class="o">,</span> <span class="n">conf</span><span class="o">,</span> <span class="n">topology</span><span class="o">.</span><span class="na">build</span><span class="o">());</span>
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-metrics-profiling-internal-actions.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-metrics-profiling-internal-actions.html b/content/releases/1.0.6/storm-metrics-profiling-internal-actions.html
index 1072ea4..a66bc93 100644
--- a/content/releases/1.0.6/storm-metrics-profiling-internal-actions.html
+++ b/content/releases/1.0.6/storm-metrics-profiling-internal-actions.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>With the addition of these metrics, Storm users can collect, view, and analyze the performance of various internal actions. The actions that are profiled include thrift rpc calls and http quests within the storm daemons. For instance, in the Storm Nimbus daemon, the following thrift calls defined in the Nimbus$Iface are profiled:</p>
+<div class="documentation-content"><p>With the addition of these metrics, Storm users can collect, view, and analyze the performance of various internal actions. The actions that are profiled include thrift rpc calls and http quests within the storm daemons. For instance, in the Storm Nimbus daemon, the following thrift calls defined in the Nimbus$Iface are profiled:</p>
<ul>
<li>submitTopology</li>
@@ -211,7 +211,7 @@ supervisor.childopts: "-Xmx256m -Dcom.sun.management.jmxremote.port=3337 -Dcom.s
<p>For more information about io.dropwizard.metrics and metrics-clojure packages please reference their original documentation:
- <a href="https://dropwizard.github.io/metrics/3.1.0/">https://dropwizard.github.io/metrics/3.1.0/</a>
- <a href="http://metrics-clojure.readthedocs.org/en/latest/">http://metrics-clojure.readthedocs.org/en/latest/</a></p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-mongodb.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-mongodb.html b/content/releases/1.0.6/storm-mongodb.html
index 9dd4b0f..44d6e18 100644
--- a/content/releases/1.0.6/storm-mongodb.html
+++ b/content/releases/1.0.6/storm-mongodb.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm/Trident integration for <a href="https://www.mongodb.org/">MongoDB</a>. This package includes the core bolts and trident states that allows a storm topology to either insert storm tuples in a database collection or to execute update queries against a database collection in a storm topology.</p>
+<div class="documentation-content"><p>Storm/Trident integration for <a href="https://www.mongodb.org/">MongoDB</a>. This package includes the core bolts and trident states that allows a storm topology to either insert storm tuples in a database collection or to execute update queries against a database collection in a storm topology.</p>
<h2 id="insert-into-database">Insert into Database</h2>
@@ -323,7 +323,7 @@ under the License.</p>
<ul>
<li>Sriharsha Chintalapani (<a href="mailto:sriharsha@apache.org">sriharsha@apache.org</a>)</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-mqtt.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-mqtt.html b/content/releases/1.0.6/storm-mqtt.html
index 3baf7a2..4bd9360 100644
--- a/content/releases/1.0.6/storm-mqtt.html
+++ b/content/releases/1.0.6/storm-mqtt.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h2 id="about">About</h2>
+<div class="documentation-content"><h2 id="about">About</h2>
<p>MQTT is a lightweight publish/subscribe protocol frequently used in IoT applications.</p>
@@ -483,7 +483,7 @@ keystore/truststore need to be available on all worker nodes where the spout/bol
<ul>
<li>P. Taylor Goetz (<a href="mailto:ptgoetz@apache.org">ptgoetz@apache.org</a>)</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-redis.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-redis.html b/content/releases/1.0.6/storm-redis.html
index 9885d0b..9add4ee 100644
--- a/content/releases/1.0.6/storm-redis.html
+++ b/content/releases/1.0.6/storm-redis.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm/Trident integration for <a href="http://redis.io/">Redis</a></p>
+<div class="documentation-content"><p>Storm/Trident integration for <a href="http://redis.io/">Redis</a></p>
<p>Storm-redis uses Jedis for Redis client.</p>
@@ -378,7 +378,7 @@ under the License.</p>
<li>Robert Evans (<a href="https://github.com/revans2">@revans2</a>)</li>
<li>Jungtaek Lim (<a href="https://github.com/HeartSaVioR">@HeartSaVioR</a>)</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-solr.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-solr.html b/content/releases/1.0.6/storm-solr.html
index 0314b6f..4f3a2bc 100644
--- a/content/releases/1.0.6/storm-solr.html
+++ b/content/releases/1.0.6/storm-solr.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm and Trident integration for Apache Solr. This package includes a bolt and a trident state that enable a Storm topology
+<div class="documentation-content"><p>Storm and Trident integration for Apache Solr. This package includes a bolt and a trident state that enable a Storm topology
stream the contents of storm tuples to index Solr collections.</p>
<h1 id="index-storm-tuples-into-a-solr-collection">Index Storm tuples into a Solr collection</h1>
@@ -312,7 +312,7 @@ and then generate an uber jar with all the dependencies.</p>
<p>You can also see the results by opening the Apache Solr UI and pasting the <code>id</code> pattern in the <code>q</code> textbox in the queries page</p>
<p><a href="http://localhost:8983/solr/#/gettingstarted_shard1_replica2/query">http://localhost:8983/solr/#/gettingstarted_shard1_replica2/query</a></p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-sql-internal.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-sql-internal.html b/content/releases/1.0.6/storm-sql-internal.html
index 523444e..d299f20 100644
--- a/content/releases/1.0.6/storm-sql-internal.html
+++ b/content/releases/1.0.6/storm-sql-internal.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page describes the design and the implementation of the Storm SQL integration.</p>
+<div class="documentation-content"><p>This page describes the design and the implementation of the Storm SQL integration.</p>
<h2 id="overview">Overview</h2>
@@ -191,7 +191,7 @@ INSERT INTO LARGE_ORDERS SELECT ID, UNIT_PRICE * QUANTITY AS TOTAL FROM ORDERS W
<h2 id="dependency">Dependency</h2>
<p>StormSQL does not ship the dependency of the external data sources in the packaged JAR. The users have to provide the dependency in the <code>extlib</code> directory of the worker node.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/storm-sql.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/storm-sql.html b/content/releases/1.0.6/storm-sql.html
index f93f9de..c3f3824 100644
--- a/content/releases/1.0.6/storm-sql.html
+++ b/content/releases/1.0.6/storm-sql.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>The Storm SQL integration allows users to run SQL queries over streaming data in Storm. Not only the SQL interface allows faster development cycles on streaming analytics, but also opens up the opportunities to unify batch data processing like <a href="///hive.apache.org">Apache Hive</a> and real-time streaming data analytics.</p>
+<div class="documentation-content"><p>The Storm SQL integration allows users to run SQL queries over streaming data in Storm. Not only the SQL interface allows faster development cycles on streaming analytics, but also opens up the opportunities to unify batch data processing like <a href="///hive.apache.org">Apache Hive</a> and real-time streaming data analytics.</p>
<p>At a very high level StormSQL compiles the SQL queries to <a href="Trident-API-Overview.html">Trident</a> topologies and executes them in Storm clusters. This document provides information of how to use StormSQL as end users. For people that are interested in more details in the design and the implementation of StormSQL please refer to the <a href="storm-sql-internal.html">this</a> page.</p>
@@ -231,7 +231,7 @@ zookeeper-3.4.6.jar
<p>Users also need to provide the dependency of the external data sources in the <code>extlib</code> directory. Otherwise the topology will fail to run because of <code>ClassNotFoundException</code>.</p>
<p>The current implementation of the Kafka connector in StormSQL assumes both the input and the output are in JSON formats. The connector has not yet recognized the <code>INPUTFORMAT</code> and <code>OUTPUTFORMAT</code> clauses yet.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/windows-users-guide.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/windows-users-guide.html b/content/releases/1.0.6/windows-users-guide.html
index d98adea..164bcd7 100644
--- a/content/releases/1.0.6/windows-users-guide.html
+++ b/content/releases/1.0.6/windows-users-guide.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page guides how to set up environment on Windows for Apache Storm.</p>
+<div class="documentation-content"><p>This page guides how to set up environment on Windows for Apache Storm.</p>
<h2 id="symbolic-link">Symbolic Link</h2>
@@ -172,7 +172,7 @@ If you don't want to execute Storm processes directly (not on command prompt
on Nimbus and all of the Supervisor nodes. This will also disable features that require symlinks. Currently this is only downloading
dependent blobs, but may change in the future. Some topologies may rely on symbolic links to resources in the current working directory of the worker that are
created as a convienence, so it is not a 100% backwards compatible change.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Acking-framework-implementation.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Acking-framework-implementation.html b/content/releases/1.1.2/Acking-framework-implementation.html
index 539c1fa..5300430 100644
--- a/content/releases/1.1.2/Acking-framework-implementation.html
+++ b/content/releases/1.1.2/Acking-framework-implementation.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p><a href="https://github.com/apache/incubator-storm/blob/46c3ba7/storm-core/src/clj/backtype/storm/daemon/acker.clj#L28">Storm's acker</a> tracks completion of each tupletree with a checksum hash: each time a tuple is sent, its value is XORed into the checksum, and each time a tuple is acked its value is XORed in again. If all tuples have been successfully acked, the checksum will be zero (the odds that the checksum will be zero otherwise are vanishingly small).</p>
+<div class="documentation-content"><p><a href="https://github.com/apache/incubator-storm/blob/46c3ba7/storm-core/src/clj/backtype/storm/daemon/acker.clj#L28">Storm's acker</a> tracks completion of each tupletree with a checksum hash: each time a tuple is sent, its value is XORed into the checksum, and each time a tuple is acked its value is XORed in again. If all tuples have been successfully acked, the checksum will be zero (the odds that the checksum will be zero otherwise are vanishingly small).</p>
<p>You can read a bit more about the <a href="Guaranteeing-message-processing.html#what-is-storms-reliability-api">reliability mechanism</a> elsewhere on the wiki -- this explains the internal details.</p>
@@ -180,7 +180,7 @@
<p>Internally, it holds several HashMaps ('buckets') of its own, each holding a cohort of records that will expire at the same time. Let's call the longest-lived bucket death row, and the most recent the nursery. Whenever a value is <code>.put()</code> to the RotatingMap, it is relocated to the nursery -- and removed from any other bucket it might have been in (effectively resetting its death clock).</p>
<p>Whenever its owner calls <code>.rotate()</code>, the RotatingMap advances each cohort one step further towards expiration. (Typically, Storm objects call rotate on every receipt of a system tick stream tuple.) If there are any key-value pairs in the former death row bucket, the RotatingMap invokes a callback (given in the constructor) for each key-value pair, letting its owner take appropriate action (eg, failing a tuple.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Clojure-DSL.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Clojure-DSL.html b/content/releases/1.1.2/Clojure-DSL.html
index 65eb4cd..c42d15c 100644
--- a/content/releases/1.1.2/Clojure-DSL.html
+++ b/content/releases/1.1.2/Clojure-DSL.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm comes with a Clojure DSL for defining spouts, bolts, and topologies. The Clojure DSL has access to everything the Java API exposes, so if you're a Clojure user you can code Storm topologies without touching Java at all. The Clojure DSL is defined in the source in the <a href="http://github.com/apache/storm/blob/v1.1.2/storm-core/src/clj/org/apache/storm/clojure.clj">org.apache.storm.clojure</a> namespace.</p>
+<div class="documentation-content"><p>Storm comes with a Clojure DSL for defining spouts, bolts, and topologies. The Clojure DSL has access to everything the Java API exposes, so if you're a Clojure user you can code Storm topologies without touching Java at all. The Clojure DSL is defined in the source in the <a href="http://github.com/apache/storm/blob/v1.1.2/storm-core/src/clj/org/apache/storm/clojure.clj">org.apache.storm.clojure</a> namespace.</p>
<p>This page outlines all the pieces of the Clojure DSL, including:</p>
@@ -371,7 +371,7 @@
<h3 id="testing-topologies">Testing topologies</h3>
<p><a href="http://www.pixelmachine.org/2011/12/17/Testing-Storm-Topologies.html">This blog post</a> and its <a href="http://www.pixelmachine.org/2011/12/21/Testing-Storm-Topologies-Part-2.html">follow-up</a> give a good overview of Storm's powerful built-in facilities for testing topologies in Clojure.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Command-line-client.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Command-line-client.html b/content/releases/1.1.2/Command-line-client.html
index 21af14d..25abb98 100644
--- a/content/releases/1.1.2/Command-line-client.html
+++ b/content/releases/1.1.2/Command-line-client.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page describes all the commands that are possible with the "storm" command line client. To learn how to set up your "storm" client to talk to a remote cluster, follow the instructions in <a href="Setting-up-development-environment.html">Setting up development environment</a>.</p>
+<div class="documentation-content"><p>This page describes all the commands that are possible with the "storm" command line client. To learn how to set up your "storm" client to talk to a remote cluster, follow the instructions in <a href="Setting-up-development-environment.html">Setting up development environment</a>.</p>
<p>These commands are:</p>
@@ -423,7 +423,7 @@ and timeout is integer seconds.</p>
<p>Syntax: <code>storm help [command]</code></p>
<p>Print one help message or list of available commands</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Common-patterns.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Common-patterns.html b/content/releases/1.1.2/Common-patterns.html
index 8a76bee..b0890a9 100644
--- a/content/releases/1.1.2/Common-patterns.html
+++ b/content/releases/1.1.2/Common-patterns.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page lists a variety of common patterns in Storm topologies.</p>
+<div class="documentation-content"><p>This page lists a variety of common patterns in Storm topologies.</p>
<ol>
<li>Batching</li>
@@ -212,7 +212,7 @@
<p><code>KeyedFairBolt</code> also wraps the bolt containing your logic and makes sure your topology processes multiple DRPC invocations at the same time, instead of doing them serially one at a time.</p>
<p>See <a href="Distributed-RPC.html">Distributed RPC</a> for more details.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Concepts.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Concepts.html b/content/releases/1.1.2/Concepts.html
index a08d6ba..ef1c678 100644
--- a/content/releases/1.1.2/Concepts.html
+++ b/content/releases/1.1.2/Concepts.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page lists the main concepts of Storm and links to resources where you can find more information. The concepts discussed are:</p>
+<div class="documentation-content"><p>This page lists the main concepts of Storm and links to resources where you can find more information. The concepts discussed are:</p>
<ol>
<li>Topologies</li>
@@ -268,7 +268,7 @@
<ul>
<li><a href="javadocs/org/apache/storm/Config.html#TOPOLOGY_WORKERS">Config.TOPOLOGY_WORKERS</a>: this config sets the number of workers to allocate for executing the topology</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Configuration.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Configuration.html b/content/releases/1.1.2/Configuration.html
index 9f5c91e..7afea1f 100644
--- a/content/releases/1.1.2/Configuration.html
+++ b/content/releases/1.1.2/Configuration.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm has a variety of configurations for tweaking the behavior of nimbus, supervisors, and running topologies. Some configurations are system configurations and cannot be modified on a topology by topology basis, whereas other configurations can be modified per topology. </p>
+<div class="documentation-content"><p>Storm has a variety of configurations for tweaking the behavior of nimbus, supervisors, and running topologies. Some configurations are system configurations and cannot be modified on a topology by topology basis, whereas other configurations can be modified per topology. </p>
<p>Every configuration has a default value defined in <a href="http://github.com/apache/storm/blob/v1.1.2/conf/defaults.yaml">defaults.yaml</a> in the Storm codebase. You can override these configurations by defining a storm.yaml in the classpath of Nimbus and the supervisors. Finally, you can define a topology-specific configuration that you submit along with your topology when using <a href="javadocs/org/apache/storm/StormSubmitter.html">StormSubmitter</a>. However, the topology-specific configuration can only override configs prefixed with "TOPOLOGY".</p>
@@ -175,7 +175,7 @@
<li><a href="Running-topologies-on-a-production-cluster.html">Running topologies on a production cluster</a>: lists useful configurations when running topologies on a cluster</li>
<li><a href="Local-mode.html">Local mode</a>: lists useful configurations when using local mode</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Contributing-to-Storm.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Contributing-to-Storm.html b/content/releases/1.1.2/Contributing-to-Storm.html
index 3260ba8..9884bb1 100644
--- a/content/releases/1.1.2/Contributing-to-Storm.html
+++ b/content/releases/1.1.2/Contributing-to-Storm.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h3 id="getting-started-with-contributing">Getting started with contributing</h3>
+<div class="documentation-content"><h3 id="getting-started-with-contributing">Getting started with contributing</h3>
<p>Some of the issues on the <a href="https://issues.apache.org/jira/browse/STORM">issue tracker</a> are marked with the <a href="https://issues.apache.org/jira/browse/STORM-2891?jql=project%20%3D%20STORM%20AND%20status%20%3D%20Open%20AND%20labels%20in%20(newbie%2C%20%22newbie%2B%2B%22)">"Newbie"</a> label. If you're interested in contributing to Storm but don't know where to begin, these are good issues to start with. These issues are a great way to get your feet wet with learning the codebase because they require learning about only an isolated portion of the codebase and are a relatively small amount of work.</p>
@@ -172,7 +172,7 @@
<h3 id="contributing-documentation">Contributing documentation</h3>
<p>Documentation contributions are very welcome! The best way to send contributions is as emails through the mailing list.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Creating-a-new-Storm-project.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Creating-a-new-Storm-project.html b/content/releases/1.1.2/Creating-a-new-Storm-project.html
index 6fece99..c05609a 100644
--- a/content/releases/1.1.2/Creating-a-new-Storm-project.html
+++ b/content/releases/1.1.2/Creating-a-new-Storm-project.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page outlines how to set up a Storm project for development. The steps are:</p>
+<div class="documentation-content"><p>This page outlines how to set up a Storm project for development. The steps are:</p>
<ol>
<li>Add Storm jars to classpath</li>
@@ -166,7 +166,7 @@
<p>For more information on writing topologies in other languages, see <a href="Using-non-JVM-languages-with-Storm.html">Using non-JVM languages with Storm</a>.</p>
<p>To test that everything is working in Eclipse, you should now be able to <code>Run</code> the <code>WordCountTopology.java</code> file. You will see messages being emitted at the console for 10 seconds.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/DSLs-and-multilang-adapters.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/DSLs-and-multilang-adapters.html b/content/releases/1.1.2/DSLs-and-multilang-adapters.html
index e50dc7d..b96ceb1 100644
--- a/content/releases/1.1.2/DSLs-and-multilang-adapters.html
+++ b/content/releases/1.1.2/DSLs-and-multilang-adapters.html
@@ -144,14 +144,14 @@
<p class="post-meta"></p>
-<ul>
+<div class="documentation-content"><ul>
<li><a href="https://github.com/velvia/ScalaStorm">Scala DSL</a></li>
<li><a href="https://github.com/colinsurprenant/redstorm">JRuby DSL</a></li>
<li><a href="Clojure-DSL.html">Clojure DSL</a></li>
<li><a href="https://github.com/tomdz/storm-esper">Storm/Esper integration</a>: Streaming SQL on top of Storm</li>
<li><a href="https://github.com/dan-blanchard/io-storm">io-storm</a>: Perl multilang adapter</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.1.2/Daemon-Fault-Tolerance.html
----------------------------------------------------------------------
diff --git a/content/releases/1.1.2/Daemon-Fault-Tolerance.html b/content/releases/1.1.2/Daemon-Fault-Tolerance.html
index e494fef..dfddcec 100644
--- a/content/releases/1.1.2/Daemon-Fault-Tolerance.html
+++ b/content/releases/1.1.2/Daemon-Fault-Tolerance.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm has several different daemon processes. Nimbus that schedules workers, supervisors that launch and kill workers, the log viewer that gives access to logs, and the UI that shows the status of a cluster.</p>
+<div class="documentation-content"><p>Storm has several different daemon processes. Nimbus that schedules workers, supervisors that launch and kill workers, the log viewer that gives access to logs, and the UI that shows the status of a cluster.</p>
<h2 id="what-happens-when-a-worker-dies">What happens when a worker dies?</h2>
@@ -169,7 +169,7 @@
<h2 id="how-does-storm-guarantee-data-processing">How does Storm guarantee data processing?</h2>
<p>Storm provides mechanisms to guarantee data processing even if nodes die or messages are lost. See <a href="Guaranteeing-message-processing.html">Guaranteeing message processing</a> for the details.</p>
-
+</div>
</div>