You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by bo...@apache.org on 2016/04/07 16:32:03 UTC
svn commit: r1738133 [8/9] - in /storm/site: _includes/ about/ publish/
publish/2012/08/02/ publish/2012/09/06/ publish/2013/01/11/
publish/2013/12/08/ publish/2014/04/10/ publish/2014/04/17/
publish/2014/04/19/ publish/2014/04/21/ publish/2014/04/22/ ...
Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/storm-mqtt.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/storm-mqtt.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/2.0.0-SNAPSHOT/storm-mqtt.html (original)
+++ storm/site/publish/releases/2.0.0-SNAPSHOT/storm-mqtt.html Thu Apr 7 14:32:00 2016
@@ -365,12 +365,12 @@ something like the following:</p>
<span class="k">return</span> <span class="n">builder</span><span class="o">.</span><span class="na">createTopology</span><span class="o">();</span>
</code></pre></div>
-<h2 id="ssl-tls">SSL/TLS</h2>
+<h2 id="ssl/tls">SSL/TLS</h2>
<p>If the MQTT broker you are connecting to requires SSL or SSL client authentication, you need to configure the spout
with an appropriate URI, and the location of keystore/truststore files containing the necessary certificates.</p>
-<h3 id="ssl-tls-uris">SSL/TLS URIs</h3>
+<h3 id="ssl/tls-uris">SSL/TLS URIs</h3>
<p>To connect over SSL/TLS use a URI with a prefix of <code>ssl://</code> or <code>tls://</code> instead of <code>tcp://</code>. For further control over
the algorithm, you can specify a specific protocol:</p>
@@ -382,7 +382,7 @@ the algorithm, you can specify a specifi
<li><code>tlsv*://</code> Use a specific version of the TLS protocol, where <code>*</code> is replaced by the version (e.g. <code>tlsv1.1://</code>)</li>
</ul>
-<h3 id="specifying-keystore-truststore-locations">Specifying Keystore/Truststore Locations</h3>
+<h3 id="specifying-keystore/truststore-locations">Specifying Keystore/Truststore Locations</h3>
<p>The <code>MqttSpout</code>, <code>MqttBolt</code> and <code>MqttPublishFunction</code> all have constructors that take a <code>KeyStoreLoader</code> instance that
is used to load the certificates required for TLS/SSL connections. For example:</p>
@@ -508,7 +508,7 @@ keystore/truststore need to be available
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/storm-redis.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/storm-redis.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/2.0.0-SNAPSHOT/storm-redis.html (original)
+++ storm/site/publish/releases/2.0.0-SNAPSHOT/storm-redis.html Thu Apr 7 14:32:00 2016
@@ -134,7 +134,7 @@
<h2 id="usage">Usage</h2>
-<h3 id="how-do-i-use-it">How do I use it?</h3>
+<h3 id="how-do-i-use-it?">How do I use it?</h3>
<p>use it as a maven dependency:</p>
<div class="highlight"><pre><code class="language-xml" data-lang="xml"><span class="nt"><dependency></span>
@@ -403,7 +403,7 @@ under the License.</p>
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/storm-solr.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/storm-solr.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/2.0.0-SNAPSHOT/storm-solr.html (original)
+++ storm/site/publish/releases/2.0.0-SNAPSHOT/storm-solr.html Thu Apr 7 14:32:00 2016
@@ -337,7 +337,7 @@ and then generate an uber jar with all t
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/storm-sql-internal.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/storm-sql-internal.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/2.0.0-SNAPSHOT/storm-sql-internal.html (original)
+++ storm/site/publish/releases/2.0.0-SNAPSHOT/storm-sql-internal.html Thu Apr 7 14:32:00 2016
@@ -216,7 +216,7 @@ INSERT INTO LARGE_ORDERS SELECT ID, UNIT
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/storm-sql.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/storm-sql.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/2.0.0-SNAPSHOT/storm-sql.html (original)
+++ storm/site/publish/releases/2.0.0-SNAPSHOT/storm-sql.html Thu Apr 7 14:32:00 2016
@@ -168,7 +168,7 @@
<p>Users plug in external data sources through implementing the <code>ISqlTridentDataSource</code> interface and registers them using the mechanisms of Java's service loader. The external data source will be chosen based on the scheme of the URI of the tables. Please refer to the implementation of <code>storm-sql-kafka</code> for more details.</p>
-<h2 id="example-filtering-kafka-stream">Example: Filtering Kafka Stream</h2>
+<h2 id="example:-filtering-kafka-stream">Example: Filtering Kafka Stream</h2>
<p>Let's say there is a Kafka stream that represents the transactions of orders. Each message in the stream contains the id of the order, the unit price of the product and the quantity of the orders. The goal is to filter orders where the transactions are significant and to insert these orders into another Kafka stream for further analysis.</p>
@@ -243,7 +243,7 @@ $ cp storm-kafka-*.jar storm-sql-kafka-*
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/2.0.0-SNAPSHOT/windows-users-guide.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/2.0.0-SNAPSHOT/windows-users-guide.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/2.0.0-SNAPSHOT/windows-users-guide.html (original)
+++ storm/site/publish/releases/2.0.0-SNAPSHOT/windows-users-guide.html Thu Apr 7 14:32:00 2016
@@ -186,7 +186,7 @@ If you don't want to execute Storm p
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Clojure-DSL.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Clojure-DSL.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Clojure-DSL.html (original)
+++ storm/site/publish/releases/current/Clojure-DSL.html Thu Apr 7 14:32:00 2016
@@ -283,7 +283,7 @@
</span></code></pre></div>
<p>This declares the output of the bolt as the fields ["word" "count"] on the default stream id.</p>
-<h4 id="emitting-acking-and-failing">Emitting, acking, and failing</h4>
+<h4 id="emitting,-acking,-and-failing">Emitting, acking, and failing</h4>
<p>Rather than use the Java methods on <code>OutputCollector</code> directly, the DSL provides a nicer set of functions for using <code>OutputCollector</code>: <code>emit-bolt!</code>, <code>emit-direct-bolt!</code>, <code>ack!</code>, and <code>fail!</code>.</p>
@@ -396,7 +396,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Command-line-client.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Command-line-client.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Command-line-client.html (original)
+++ storm/site/publish/releases/current/Command-line-client.html Thu Apr 7 14:32:00 2016
@@ -270,7 +270,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Common-patterns.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Common-patterns.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Common-patterns.html (original)
+++ storm/site/publish/releases/current/Common-patterns.html Thu Apr 7 14:32:00 2016
@@ -164,7 +164,7 @@
<p>Many bolts follow a similar pattern of reading an input tuple, emitting zero or more tuples based on that input tuple, and then acking that input tuple immediately at the end of the execute method. Bolts that match this pattern are things like functions and filters. This is such a common pattern that Storm exposes an interface called <a href="javadocs/backtype/storm/topology/IBasicBolt.html">IBasicBolt</a> that automates this pattern for you. See <a href="Guaranteeing-message-processing.html">Guaranteeing message processing</a> for more information.</p>
-<h3 id="in-memory-caching-fields-grouping-combo">In-memory caching + fields grouping combo</h3>
+<h3 id="in-memory-caching-+-fields-grouping-combo">In-memory caching + fields grouping combo</h3>
<p>It's common to keep caches in-memory in Storm bolts. Caching becomes particularly powerful when you combine it with a fields grouping. For example, suppose you have a bolt that expands short URLs (like bit.ly, t.co, etc.) into long URLs. You can increase performance by keeping an LRU cache of short URL to long URL expansions to avoid doing the same HTTP requests over and over. Suppose component "urls" emits short URLS, and component "expand" expands short URLs into long URLs and keeps a cache internally. Consider the difference between the two following snippets of code:</p>
<div class="highlight"><pre><code class="language-java" data-lang="java"><span class="n">builder</span><span class="o">.</span><span class="na">setBolt</span><span class="o">(</span><span class="s">"expand"</span><span class="o">,</span> <span class="k">new</span> <span class="n">ExpandUrl</span><span class="o">(),</span> <span class="n">parallelism</span><span class="o">)</span>
@@ -250,7 +250,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Concepts.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Concepts.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Concepts.html (original)
+++ storm/site/publish/releases/current/Concepts.html Thu Apr 7 14:32:00 2016
@@ -293,7 +293,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Configuration.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Configuration.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Configuration.html (original)
+++ storm/site/publish/releases/current/Configuration.html Thu Apr 7 14:32:00 2016
@@ -200,7 +200,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Contributing-to-Storm.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Contributing-to-Storm.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Contributing-to-Storm.html (original)
+++ storm/site/publish/releases/current/Contributing-to-Storm.html Thu Apr 7 14:32:00 2016
@@ -197,7 +197,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Creating-a-new-Storm-project.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Creating-a-new-Storm-project.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Creating-a-new-Storm-project.html (original)
+++ storm/site/publish/releases/current/Creating-a-new-Storm-project.html Thu Apr 7 14:32:00 2016
@@ -143,7 +143,7 @@
<p>To set up the classpath in Eclipse, create a new Java project, include <code>src/jvm/</code> as a source path, and make sure all the jars in <code>lib/</code> and <code>lib/dev/</code> are in the <code>Referenced Libraries</code> section of the project.</p>
-<h3 id="if-using-multilang-add-multilang-dir-to-classpath">If using multilang, add multilang dir to classpath</h3>
+<h3 id="if-using-multilang,-add-multilang-dir-to-classpath">If using multilang, add multilang dir to classpath</h3>
<p>If you implement spouts or bolts in languages other than Java, then those implementations should be under the <code>multilang/resources/</code> directory of the project. For Storm to find these files in local mode, the <code>resources/</code> dir needs to be on the classpath. You can do this in Eclipse by adding <code>multilang/</code> as a source folder. You may also need to add multilang/resources as a source directory.</p>
@@ -191,7 +191,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/DSLs-and-multilang-adapters.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/DSLs-and-multilang-adapters.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/DSLs-and-multilang-adapters.html (original)
+++ storm/site/publish/releases/current/DSLs-and-multilang-adapters.html Thu Apr 7 14:32:00 2016
@@ -176,7 +176,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Daemon-Fault-Tolerance.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Daemon-Fault-Tolerance.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Daemon-Fault-Tolerance.html (original)
+++ storm/site/publish/releases/current/Daemon-Fault-Tolerance.html Thu Apr 7 14:32:00 2016
@@ -130,27 +130,27 @@
<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>
+<h2 id="what-happens-when-a-worker-dies?">What happens when a worker dies?</h2>
<p>When a worker dies, the supervisor will restart it. If it continuously fails on startup and is unable to heartbeat to Nimbus, Nimbus will reschedule the worker.</p>
-<h2 id="what-happens-when-a-node-dies">What happens when a node dies?</h2>
+<h2 id="what-happens-when-a-node-dies?">What happens when a node dies?</h2>
<p>The tasks assigned to that machine will time-out and Nimbus will reassign those tasks to other machines.</p>
-<h2 id="what-happens-when-nimbus-or-supervisor-daemons-die">What happens when Nimbus or Supervisor daemons die?</h2>
+<h2 id="what-happens-when-nimbus-or-supervisor-daemons-die?">What happens when Nimbus or Supervisor daemons die?</h2>
<p>The Nimbus and Supervisor daemons are designed to be fail-fast (process self-destructs whenever any unexpected situation is encountered) and stateless (all state is kept in Zookeeper or on disk). As described in <a href="Setting-up-a-Storm-cluster.html">Setting up a Storm cluster</a>, the Nimbus and Supervisor daemons must be run under supervision using a tool like daemontools or monit. So if the Nimbus or Supervisor daemons die, they restart like nothing happened.</p>
<p>Most notably, no worker processes are affected by the death of Nimbus or the Supervisors. This is in contrast to Hadoop, where if the JobTracker dies, all the running jobs are lost. </p>
-<h2 id="is-nimbus-a-single-point-of-failure">Is Nimbus a single point of failure?</h2>
+<h2 id="is-nimbus-a-single-point-of-failure?">Is Nimbus a single point of failure?</h2>
<p>If you lose the Nimbus node, the workers will still continue to function. Additionally, supervisors will continue to restart workers if they die. However, without Nimbus, workers won't be reassigned to other machines when necessary (like if you lose a worker machine). </p>
<p>So the answer is that Nimbus is "sort of" a SPOF. In practice, it's not a big deal since nothing catastrophic happens when the Nimbus daemon dies. There are plans to make Nimbus highly available in the future.</p>
-<h2 id="how-does-storm-guarantee-data-processing">How does Storm guarantee data processing?</h2>
+<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>
@@ -194,7 +194,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Defining-a-non-jvm-language-dsl-for-storm.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Defining-a-non-jvm-language-dsl-for-storm.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Defining-a-non-jvm-language-dsl-for-storm.html (original)
+++ storm/site/publish/releases/current/Defining-a-non-jvm-language-dsl-for-storm.html Thu Apr 7 14:32:00 2016
@@ -190,7 +190,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Distributed-RPC.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Distributed-RPC.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Distributed-RPC.html (original)
+++ storm/site/publish/releases/current/Distributed-RPC.html Thu Apr 7 14:32:00 2016
@@ -355,7 +355,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/FAQ.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/FAQ.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/FAQ.html (original)
+++ storm/site/publish/releases/current/FAQ.html Thu Apr 7 14:32:00 2016
@@ -130,7 +130,7 @@
<h2 id="best-practices">Best Practices</h2>
-<h3 id="what-rules-of-thumb-can-you-give-me-for-configuring-storm-trident">What rules of thumb can you give me for configuring Storm+Trident?</h3>
+<h3 id="what-rules-of-thumb-can-you-give-me-for-configuring-storm+trident?">What rules of thumb can you give me for configuring Storm+Trident?</h3>
<ul>
<li>number of workers a multiple of number of machines; parallelism a multiple of number of workers; number of kafka partitions a multiple of number of spout parallelism</li>
@@ -143,7 +143,7 @@
<li>Start with a max spout pending that is for sure too small -- one for trident, or the number of executors for storm -- and increase it until you stop seeing changes in the flow. You'll probably end up with something near <code>2*(throughput in recs/sec)*(end-to-end latency)</code> (2x the Little's law capacity).</li>
</ul>
-<h3 id="what-are-some-of-the-best-ways-to-get-a-worker-to-mysteriously-and-bafflingly-die">What are some of the best ways to get a worker to mysteriously and bafflingly die?</h3>
+<h3 id="what-are-some-of-the-best-ways-to-get-a-worker-to-mysteriously-and-bafflingly-die?">What are some of the best ways to get a worker to mysteriously and bafflingly die?</h3>
<ul>
<li>Do you have write access to the log directory</li>
@@ -154,7 +154,7 @@
<li>Have you opened firewall/securitygroup permissions <em>bidirectionally</em> among a) all the workers, b) the storm master, c) zookeeper? Also, from the workers to any kafka/kestrel/database/etc that your topology accesses? Use netcat to poke the appropriate ports and be sure. </li>
</ul>
-<h3 id="halp-i-cannot-see">Halp! I cannot see:</h3>
+<h3 id="halp!-i-cannot-see:">Halp! I cannot see:</h3>
<ul>
<li><strong>my logs</strong> Logs by default go to $STORM_HOME/logs. Check that you have write permissions to that directory. They are configured in log4j2/{cluster, worker}.xml.</li>
@@ -162,7 +162,7 @@
<li><strong>final Java system properties</strong> Add <code>Properties props = System.getProperties(); props.list(System.out);</code> near where you build your topology.</li>
</ul>
-<h3 id="how-many-workers-should-i-use">How many Workers should I use?</h3>
+<h3 id="how-many-workers-should-i-use?">How many Workers should I use?</h3>
<p>The total number of workers is set by the supervisors -- there's some number of JVM slots each supervisor will superintend. The thing you set on the topology is how many worker slots it will try to claim.</p>
@@ -178,7 +178,7 @@
<h2 id="topology">Topology</h2>
-<h3 id="can-a-trident-topology-have-multiple-streams">Can a Trident topology have Multiple Streams?</h3>
+<h3 id="can-a-trident-topology-have-multiple-streams?">Can a Trident topology have Multiple Streams?</h3>
<blockquote>
<p>Can a Trident Topology work like a workflow with conditional paths (if-else)? e.g. A Spout (S1) connects to a bolt (B0) which based on certain values in the incoming tuple routes them to either bolt (B1) or bolt (B2) but not both.</p>
@@ -193,29 +193,29 @@
<p>At time of writing, you can't emit to multiple output streams from Trident -- see <a href="https://issues.apache.org/jira/browse/STORM-68">STORM-68</a></p>
-<h3 id="why-am-i-getting-a-notserializableexception-illegalstateexception-when-my-topology-is-being-started-up">Why am I getting a NotSerializableException/IllegalStateException when my topology is being started up?</h3>
+<h3 id="why-am-i-getting-a-notserializableexception/illegalstateexception-when-my-topology-is-being-started-up?">Why am I getting a NotSerializableException/IllegalStateException when my topology is being started up?</h3>
<p>Within the Storm lifecycle, the topology is instantiated and then serialized to byte format to be stored in ZooKeeper, prior to the topology being executed. Within this step, if a spout or bolt within the topology has an initialized unserializable property, serialization will fail. If there is a need for a field that is unserializable, initialize it within the bolt or spout's prepare method, which is run after the topology is delivered to the worker.</p>
<h2 id="spouts">Spouts</h2>
-<h3 id="what-is-a-coordinator-and-why-are-there-several">What is a coordinator, and why are there several?</h3>
+<h3 id="what-is-a-coordinator,-and-why-are-there-several?">What is a coordinator, and why are there several?</h3>
<p>A trident-spout is actually run within a storm <em>bolt</em>. The storm-spout of a trident topology is the MasterBatchCoordinator -- it coordinates trident batches and is the same no matter what spouts you use. A batch is born when the MBC dispenses a seed tuple to each of the spout-coordinators. The spout-coordinator bolts know how your particular spouts should cooperate -- so in the kafka case, it's what helps figure out what partition and offset range each spout should pull from.</p>
-<h3 id="what-can-i-store-into-the-spout-39-s-metadata-record">What can I store into the spout's metadata record?</h3>
+<h3 id="what-can-i-store-into-the-spout's-metadata-record?">What can I store into the spout's metadata record?</h3>
<p>You should only store static data, and as little of it as possible, into the metadata record (note: maybe you <em>can</em> store more interesting things; you shouldn't, though)</p>
-<h3 id="how-often-is-the-39-emitpartitionbatchnew-39-function-called">How often is the 'emitPartitionBatchNew' function called?</h3>
+<h3 id="how-often-is-the-'emitpartitionbatchnew'-function-called?">How often is the 'emitPartitionBatchNew' function called?</h3>
<p>Since the MBC is the actual spout, all the tuples in a batch are just members of its tupletree. That means storm's "max spout pending" config effectively defines the number of concurrent batches trident runs. The MBC emits a new batch if it has fewer than max-spending tuples pending and if at least one <a href="http://github.com/apache/storm/blob/v0.10.0/conf/defaults.yaml#L115">trident batch interval</a>'s worth of seconds has passed since the last batch.</p>
-<h3 id="if-nothing-was-emitted-does-trident-slow-down-the-calls">If nothing was emitted does Trident slow down the calls?</h3>
+<h3 id="if-nothing-was-emitted-does-trident-slow-down-the-calls?">If nothing was emitted does Trident slow down the calls?</h3>
<p>Yes, there's a pluggable "spout wait strategy"; the default is to sleep for a <a href="http://github.com/apache/storm/blob/v0.10.0/conf/defaults.yaml#L110">configurable amount of time</a></p>
-<h3 id="ok-then-what-is-the-trident-batch-interval-for">OK, then what is the trident batch interval for?</h3>
+<h3 id="ok,-then-what-is-the-trident-batch-interval-for?">OK, then what is the trident batch interval for?</h3>
<p>You know how computers of the 486 era had a <a href="http://en.wikipedia.org/wiki/Turbo_button">turbo button</a> on them? It's like that. </p>
@@ -225,11 +225,11 @@
<p>Note that this is a cap, not an additional delay -- with a period of 300ms, if your batch takes 258ms Trident will only delay an additional 42ms.</p>
-<h3 id="how-do-you-set-the-batch-size">How do you set the batch size?</h3>
+<h3 id="how-do-you-set-the-batch-size?">How do you set the batch size?</h3>
<p>Trident doesn't place its own limits on the batch count. In the case of the Kafka spout, the max fetch bytes size divided by the average record size defines an effective records per subbatch partition.</p>
-<h3 id="how-do-i-resize-a-batch">How do I resize a batch?</h3>
+<h3 id="how-do-i-resize-a-batch?">How do I resize a batch?</h3>
<p>The trident batch is a somewhat overloaded facility. Together with the number of partitions, the batch size is constrained by or serves to define</p>
@@ -244,13 +244,13 @@
<h2 id="time-series">Time Series</h2>
-<h3 id="how-do-i-aggregate-events-by-time">How do I aggregate events by time?</h3>
+<h3 id="how-do-i-aggregate-events-by-time?">How do I aggregate events by time?</h3>
<p>If you have records with an immutable timestamp, and you would like to count, average or otherwise aggregate them into discrete time buckets, Trident is an excellent and scalable solution.</p>
<p>Write an <code>Each</code> function that turns the timestamp into a time bucket: if the bucket size was "by hour", then the timestamp <code>2013-08-08 12:34:56</code> would be mapped to the <code>2013-08-08 12:00:00</code> time bucket, and so would everything else in the twelve o'clock hour. Then group on that timebucket and use a grouped persistentAggregate. The persistentAggregate uses a local cacheMap backed by a data store. Groups with many records require very few reads from the data store, and use efficient bulk reads and writes; as long as your data feed is relatively prompt Trident will make very efficient use of memory and network. Even if a server drops off line for a day, then delivers that full day's worth of data in a rush, the old results will be calmly retrieved and updated -- and without interfering with calculating the current results.</p>
-<h3 id="how-can-i-know-that-all-records-for-a-time-bucket-have-been-received">How can I know that all records for a time bucket have been received?</h3>
+<h3 id="how-can-i-know-that-all-records-for-a-time-bucket-have-been-received?">How can I know that all records for a time bucket have been received?</h3>
<p>You cannot know that all events are collected -- this is an epistemological challenge, not a distributed systems challenge. You can:</p>
@@ -301,7 +301,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Guaranteeing-message-processing.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Guaranteeing-message-processing.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Guaranteeing-message-processing.html (original)
+++ storm/site/publish/releases/current/Guaranteeing-message-processing.html Thu Apr 7 14:32:00 2016
@@ -131,7 +131,7 @@
<p>Storm offers several different levels of guaranteed message processing, includeing best effort, at least once, and exactly once through <a href="Trident-tutorial.html">Trident</a>.
This page describes how Storm can guarantee at least once processing.</p>
-<h3 id="what-does-it-mean-for-a-message-to-be-quot-fully-processed-quot">What does it mean for a message to be "fully processed"?</h3>
+<h3 id="what-does-it-mean-for-a-message-to-be-"fully-processed"?">What does it mean for a message to be "fully processed"?</h3>
<p>A tuple coming off a spout can trigger thousands of tuples to be created based on it. Consider, for example, the streaming word count topology:</p>
<div class="highlight"><pre><code class="language-java" data-lang="java"><span class="n">TopologyBuilder</span> <span class="n">builder</span> <span class="o">=</span> <span class="k">new</span> <span class="n">TopologyBuilder</span><span class="o">();</span>
@@ -150,7 +150,7 @@ This page describes how Storm can guaran
<p>Storm considers a tuple coming off a spout "fully processed" when the tuple tree has been exhausted and every message in the tree has been processed. A tuple is considered failed when its tree of messages fails to be fully processed within a specified timeout. This timeout can be configured on a topology-specific basis using the <a href="javadocs/backtype/storm/Config.html#TOPOLOGY_MESSAGE_TIMEOUT_SECS">Config.TOPOLOGY_MESSAGE_TIMEOUT_SECS</a> configuration and defaults to 30 seconds.</p>
-<h3 id="what-happens-if-a-message-is-fully-processed-or-fails-to-be-fully-processed">What happens if a message is fully processed or fails to be fully processed?</h3>
+<h3 id="what-happens-if-a-message-is-fully-processed-or-fails-to-be-fully-processed?">What happens if a message is fully processed or fails to be fully processed?</h3>
<p>To understand this question, let's take a look at the lifecycle of a tuple coming off of a spout. For reference, here is the interface that spouts implement (see the <a href="javadocs/backtype/storm/spout/ISpout.html">Javadoc</a> for more information):</p>
<div class="highlight"><pre><code class="language-java" data-lang="java"><span class="kd">public</span> <span class="kd">interface</span> <span class="nc">ISpout</span> <span class="kd">extends</span> <span class="n">Serializable</span> <span class="o">{</span>
@@ -168,7 +168,7 @@ This page describes how Storm can guaran
<p>Let's use <code>KestrelSpout</code> again to see what a <code>Spout</code> needs to do to guarantee message processing. When <code>KestrelSpout</code> takes a message off the Kestrel queue, it "opens" the message. This means the message is not actually taken off the queue yet, but instead placed in a "pending" state waiting for acknowledgement that the message is completed. While in the pending state, a message will not be sent to other consumers of the queue. Additionally, if a client disconnects all pending messages for that client are put back on the queue. When a message is opened, Kestrel provides the client with the data for the message as well as a unique id for the message. The <code>KestrelSpout</code> uses that exact id as the "message id" for the tuple when emitting the tuple to the <code>SpoutOutputCollector</code>. Sometime later on, when <code>ack</code> or <code>fail</code> are called on the <code>KestrelSpout</code>, the <code>Kes
trelSpout</code> sends an ack or fail message to Kestrel with the message id to take the message off the queue or have it put back on.</p>
-<h3 id="what-is-storm-39-s-reliability-api">What is Storm's reliability API?</h3>
+<h3 id="what-is-storm's-reliability-api?">What is Storm's reliability API?</h3>
<p>There's two things you have to do as a user to benefit from Storm's reliability capabilities. First, you need to tell Storm whenever you're creating a new link in the tree of tuples. Second, you need to tell Storm when you have finished processing an individual tuple. By doing both these things, Storm can detect when the tree of tuples is fully processed and can ack or fail the spout tuple appropriately. Storm's API provides a concise way of doing both of these tasks. </p>
@@ -234,11 +234,11 @@ This page describes how Storm can guaran
<p>In contrast, bolts that do aggregations or joins may delay acking a tuple until after it has computed a result based on a bunch of tuples. Aggregations and joins will commonly multi-anchor their output tuples as well. These things fall outside the simpler pattern of <code>IBasicBolt</code>.</p>
-<h3 id="how-do-i-make-my-applications-work-correctly-given-that-tuples-can-be-replayed">How do I make my applications work correctly given that tuples can be replayed?</h3>
+<h3 id="how-do-i-make-my-applications-work-correctly-given-that-tuples-can-be-replayed?">How do I make my applications work correctly given that tuples can be replayed?</h3>
<p>As always in software design, the answer is "it depends." If you really want exactly once semantics use the <a href="Trident-tutorial.html">Trident</a> API. In some cases, like with a lot of analytics, dropping data is OK so disabling the fault tolerance by setting the number of acker bolts to 0 <a href="javadocs/backtype/storm/Config.html#TOPOLOGY_ACKERS">Config.TOPOLOGY_ACKERS</a>. But in some cases you want to be sure that everything was processed at least once and nothing was dropped. This is especially useful if all operations are idenpotent or if deduping can happen aferwards.</p>
-<h3 id="how-does-storm-implement-reliability-in-an-efficient-way">How does Storm implement reliability in an efficient way?</h3>
+<h3 id="how-does-storm-implement-reliability-in-an-efficient-way?">How does Storm implement reliability in an efficient way?</h3>
<p>A Storm topology has a set of special "acker" tasks that track the DAG of tuples for every spout tuple. When an acker sees that a DAG is complete, it sends a message to the spout task that created the spout tuple to ack the message. You can set the number of acker tasks for a topology in the topology configuration using <a href="javadocs/backtype/storm/Config.html#TOPOLOGY_ACKERS">Config.TOPOLOGY_ACKERS</a>. Storm defaults TOPOLOGY_ACKERS to one task per worker.</p>
@@ -326,7 +326,7 @@ This page describes how Storm can guaran
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Hooks.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Hooks.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Hooks.html (original)
+++ storm/site/publish/releases/current/Hooks.html Thu Apr 7 14:32:00 2016
@@ -175,7 +175,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Implementation-docs.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Implementation-docs.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Implementation-docs.html (original)
+++ storm/site/publish/releases/current/Implementation-docs.html Thu Apr 7 14:32:00 2016
@@ -191,7 +191,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Installing-native-dependencies.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Installing-native-dependencies.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Installing-native-dependencies.html (original)
+++ storm/site/publish/releases/current/Installing-native-dependencies.html Thu Apr 7 14:32:00 2016
@@ -200,7 +200,7 @@ sudo make install
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Kestrel-and-Storm.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Kestrel-and-Storm.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Kestrel-and-Storm.html (original)
+++ storm/site/publish/releases/current/Kestrel-and-Storm.html Thu Apr 7 14:32:00 2016
@@ -359,7 +359,7 @@ If you run the topology with TOPOLOGY_DE
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Lifecycle-of-a-topology.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Lifecycle-of-a-topology.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Lifecycle-of-a-topology.html (original)
+++ storm/site/publish/releases/current/Lifecycle-of-a-topology.html Thu Apr 7 14:32:00 2016
@@ -286,7 +286,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Local-mode.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Local-mode.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Local-mode.html (original)
+++ storm/site/publish/releases/current/Local-mode.html Thu Apr 7 14:32:00 2016
@@ -189,7 +189,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Maven.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Maven.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Maven.html (original)
+++ storm/site/publish/releases/current/Maven.html Thu Apr 7 14:32:00 2016
@@ -182,7 +182,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Message-passing-implementation.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Message-passing-implementation.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Message-passing-implementation.html (original)
+++ storm/site/publish/releases/current/Message-passing-implementation.html Thu Apr 7 14:32:00 2016
@@ -211,7 +211,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Metrics.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Metrics.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Metrics.html (original)
+++ storm/site/publish/releases/current/Metrics.html Thu Apr 7 14:32:00 2016
@@ -203,7 +203,7 @@ It's used internally to track the nu
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Multilang-protocol.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Multilang-protocol.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Multilang-protocol.html (original)
+++ storm/site/publish/releases/current/Multilang-protocol.html Thu Apr 7 14:32:00 2016
@@ -359,7 +359,7 @@ emits, however.</p>
shell bolt to 'sync'.</li>
</ul>
-<h3 id="handling-heartbeats-0-9-3-and-later">Handling Heartbeats (0.9.3 and later)</h3>
+<h3 id="handling-heartbeats-(0.9.3-and-later)">Handling Heartbeats (0.9.3 and later)</h3>
<p>As of Storm 0.9.3, heartbeats have been between ShellSpout/ShellBolt and their
multi-lang subprocesses to detect hanging/zombie subprocesses. Any libraries
@@ -429,7 +429,7 @@ ShellBolt.</p>
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Rationale.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Rationale.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Rationale.html (original)
+++ storm/site/publish/releases/current/Rationale.html Thu Apr 7 14:32:00 2016
@@ -201,7 +201,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Running-topologies-on-a-production-cluster.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Running-topologies-on-a-production-cluster.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Running-topologies-on-a-production-cluster.html (original)
+++ storm/site/publish/releases/current/Running-topologies-on-a-production-cluster.html Thu Apr 7 14:32:00 2016
@@ -237,7 +237,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/SECURITY.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/SECURITY.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/SECURITY.html (original)
+++ storm/site/publish/releases/current/SECURITY.html Thu Apr 7 14:32:00 2016
@@ -134,7 +134,7 @@
your cluster. By default all authentication and authorization is disabled but
can be turned on as needed.</p>
-<h2 id="firewall-os-level-security">Firewall/OS level Security</h2>
+<h2 id="firewall/os-level-security">Firewall/OS level Security</h2>
<p>You can still have a secure storm cluster without turning on formal
Authentication and Authorization. But to do so usually requires
@@ -211,7 +211,7 @@ IPsec to encrypt all traffic being sent
</tr>
</tbody></table>
-<h3 id="ui-logviewer">UI/Logviewer</h3>
+<h3 id="ui/logviewer">UI/Logviewer</h3>
<p>The UI and logviewer processes provide a way to not only see what a cluster is
doing, but also manipulate running topologies. In general these processes should
@@ -255,7 +255,7 @@ curl -i --negotiate -u:anyUser -b ~/co
<p><strong>Caution</strong>: In AD MIT Keberos setup the key size is bigger than the default UI jetty server request header size. Make sure you set ui.header.buffer.bytes to 65536 in storm.yaml. More details are on <a href="https://issues.apache.org/jira/browse/STORM-633">STORM-633</a></p>
-<h2 id="ui-drpc-ssl">UI / DRPC SSL</h2>
+<h2 id="ui-/-drpc-ssl">UI / DRPC SSL</h2>
<p>Both UI and DRPC allows users to configure ssl .</p>
@@ -301,7 +301,7 @@ curl -i --negotiate -u:anyUser -b ~/co
9. drpc.https.want.client.auth (If this set to true server requests for client certifcate authentication, but keeps the connection if no authentication provided)
10. drpc.https.need.client.auth (If this set to true server requires client to provide authentication)</p>
-<h2 id="authentication-kerberos">Authentication (Kerberos)</h2>
+<h2 id="authentication-(kerberos)">Authentication (Kerberos)</h2>
<p>Storm offers pluggable authentication support through thrift and SASL. This
example only goes off of Kerberos as it is a common setup for most big data
@@ -666,7 +666,7 @@ on all possible worker hosts.</p>
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/STORM-UI-REST-API.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/STORM-UI-REST-API.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/STORM-UI-REST-API.html (original)
+++ storm/site/publish/releases/current/STORM-UI-REST-API.html Thu Apr 7 14:32:00 2016
@@ -170,7 +170,7 @@ are used by nimbus.</p>
</code></pre></div>
<h2 id="get-operations">GET Operations</h2>
-<h3 id="api-v1-cluster-configuration-get">/api/v1/cluster/configuration (GET)</h3>
+<h3 id="/api/v1/cluster/configuration-(get)">/api/v1/cluster/configuration (GET)</h3>
<p>Returns the cluster configuration.</p>
@@ -195,7 +195,7 @@ are used by nimbus.</p>
</span><span class="nt">"topology.executor.send.buffer.size"</span><span class="p">:</span><span class="w"> </span><span class="mi">1024</span><span class="p">,</span><span class="w">
</span><span class="err">}</span><span class="w">
</span></code></pre></div>
-<h3 id="api-v1-cluster-summary-get">/api/v1/cluster/summary (GET)</h3>
+<h3 id="/api/v1/cluster/summary-(get)">/api/v1/cluster/summary (GET)</h3>
<p>Returns cluster summary information such as nimbus uptime or number of supervisors.</p>
@@ -267,7 +267,7 @@ are used by nimbus.</p>
</span><span class="nt">"tasksTotal"</span><span class="p">:</span><span class="w"> </span><span class="mi">28</span><span class="w">
</span><span class="p">}</span><span class="w">
</span></code></pre></div>
-<h3 id="api-v1-supervisor-summary-get">/api/v1/supervisor/summary (GET)</h3>
+<h3 id="/api/v1/supervisor/summary-(get)">/api/v1/supervisor/summary (GET)</h3>
<p>Returns summary information for all supervisors.</p>
@@ -320,7 +320,7 @@ are used by nimbus.</p>
</span><span class="p">]</span><span class="w">
</span><span class="p">}</span><span class="w">
</span></code></pre></div>
-<h3 id="api-v1-topology-summary-get">/api/v1/topology/summary (GET)</h3>
+<h3 id="/api/v1/topology/summary-(get)">/api/v1/topology/summary (GET)</h3>
<p>Returns summary information for all topologies.</p>
@@ -385,7 +385,7 @@ are used by nimbus.</p>
</span><span class="p">]</span><span class="w">
</span><span class="p">}</span><span class="w">
</span></code></pre></div>
-<h3 id="api-v1-topology-id-get">/api/v1/topology/:id (GET)</h3>
+<h3 id="/api/v1/topology/:id-(get)">/api/v1/topology/:id (GET)</h3>
<p>Returns topology information and statistics. Substitute id with topology id.</p>
@@ -777,7 +777,7 @@ are used by nimbus.</p>
</span><span class="p">}</span><span class="w">
</span><span class="p">}</span><span class="w">
</span></code></pre></div>
-<h3 id="api-v1-topology-id-component-component-get">/api/v1/topology/:id/component/:component (GET)</h3>
+<h3 id="/api/v1/topology/:id/component/:component-(get)">/api/v1/topology/:id/component/:component (GET)</h3>
<p>Returns detailed metrics and executor information</p>
@@ -1110,7 +1110,7 @@ are used by nimbus.</p>
</span></code></pre></div>
<h2 id="post-operations">POST Operations</h2>
-<h3 id="api-v1-topology-id-activate-post">/api/v1/topology/:id/activate (POST)</h3>
+<h3 id="/api/v1/topology/:id/activate-(post)">/api/v1/topology/:id/activate (POST)</h3>
<p>Activates a topology.</p>
@@ -1131,7 +1131,7 @@ are used by nimbus.</p>
<p>Sample Response:</p>
<div class="highlight"><pre><code class="language-json" data-lang="json"><span class="p">{</span><span class="nt">"topologyOperation"</span><span class="p">:</span><span class="s2">"activate"</span><span class="p">,</span><span class="nt">"topologyId"</span><span class="p">:</span><span class="s2">"wordcount-1-1420308665"</span><span class="p">,</span><span class="nt">"status"</span><span class="p">:</span><span class="s2">"success"</span><span class="p">}</span><span class="w">
</span></code></pre></div>
-<h3 id="api-v1-topology-id-deactivate-post">/api/v1/topology/:id/deactivate (POST)</h3>
+<h3 id="/api/v1/topology/:id/deactivate-(post)">/api/v1/topology/:id/deactivate (POST)</h3>
<p>Deactivates a topology.</p>
@@ -1152,7 +1152,7 @@ are used by nimbus.</p>
<p>Sample Response:</p>
<div class="highlight"><pre><code class="language-json" data-lang="json"><span class="p">{</span><span class="nt">"topologyOperation"</span><span class="p">:</span><span class="s2">"deactivate"</span><span class="p">,</span><span class="nt">"topologyId"</span><span class="p">:</span><span class="s2">"wordcount-1-1420308665"</span><span class="p">,</span><span class="nt">"status"</span><span class="p">:</span><span class="s2">"success"</span><span class="p">}</span><span class="w">
</span></code></pre></div>
-<h3 id="api-v1-topology-id-rebalance-wait-time-post">/api/v1/topology/:id/rebalance/:wait-time (POST)</h3>
+<h3 id="/api/v1/topology/:id/rebalance/:wait-time-(post)">/api/v1/topology/:id/rebalance/:wait-time (POST)</h3>
<p>Rebalances a topology.</p>
@@ -1192,7 +1192,7 @@ http://localhost:8080/api/v1/topology/wo
<p>Sample Response:</p>
<div class="highlight"><pre><code class="language-json" data-lang="json"><span class="p">{</span><span class="nt">"topologyOperation"</span><span class="p">:</span><span class="s2">"rebalance"</span><span class="p">,</span><span class="nt">"topologyId"</span><span class="p">:</span><span class="s2">"wordcount-1-1420308665"</span><span class="p">,</span><span class="nt">"status"</span><span class="p">:</span><span class="s2">"success"</span><span class="p">}</span><span class="w">
</span></code></pre></div>
-<h3 id="api-v1-topology-id-kill-wait-time-post">/api/v1/topology/:id/kill/:wait-time (POST)</h3>
+<h3 id="/api/v1/topology/:id/kill/:wait-time-(post)">/api/v1/topology/:id/kill/:wait-time (POST)</h3>
<p>Kills a topology.</p>
@@ -1272,7 +1272,7 @@ daemons.</p>
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Serialization.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Serialization.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Serialization.html (original)
+++ storm/site/publish/releases/current/Serialization.html Thu Apr 7 14:32:00 2016
@@ -225,7 +225,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Serializers.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Serializers.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Serializers.html (original)
+++ storm/site/publish/releases/current/Serializers.html Thu Apr 7 14:32:00 2016
@@ -172,7 +172,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Setting-up-a-Storm-cluster.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Setting-up-a-Storm-cluster.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Setting-up-a-Storm-cluster.html (original)
+++ storm/site/publish/releases/current/Setting-up-a-Storm-cluster.html Thu Apr 7 14:32:00 2016
@@ -168,7 +168,7 @@
<p>Next, download a Storm release and extract the zip file somewhere on Nimbus and each of the worker machines. The Storm releases can be downloaded <a href="http://github.com/apache/storm/releases">from here</a>.</p>
-<h3 id="fill-in-mandatory-configurations-into-storm-yaml">Fill in mandatory configurations into storm.yaml</h3>
+<h3 id="fill-in-mandatory-configurations-into-storm.yaml">Fill in mandatory configurations into storm.yaml</h3>
<p>The Storm release contains a file at <code>conf/storm.yaml</code> that configures the Storm daemons. You can see the default configuration values <a href="http://github.com/apache/storm/blob/v0.10.0/conf/defaults.yaml">here</a>. storm.yaml overrides anything in defaults.yaml. There's a few configurations that are mandatory to get a working cluster:</p>
@@ -216,11 +216,11 @@ You can leave it empty with default valu
The time to allow any given healthcheck script to run before it is marked failed due to timeout can be configured with:</p>
<div class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="s">storm.health.check.timeout.ms</span><span class="pi">:</span> <span class="s">5000</span>
</code></pre></div>
-<h3 id="configure-external-libraries-and-environmental-variables-optional">Configure external libraries and environmental variables (optional)</h3>
+<h3 id="configure-external-libraries-and-environmental-variables-(optional)">Configure external libraries and environmental variables (optional)</h3>
<p>If you need support from external libraries or custom plugins, you can place such jars into the extlib/ and extlib-daemon/ directories. Note that the extlib-daemon/ directory stores jars used only by daemons (Nimbus, Supervisor, DRPC, UI, Logviewer), e.g., HDFS and customized scheduling libraries. Accordingly, two environmental variables STORM_EXT_CLASSPATH and STORM_EXT_CLASSPATH_DAEMON can be configured by users for including the external classpath and daemon-only external classpath.</p>
-<h3 id="launch-daemons-under-supervision-using-quot-storm-quot-script-and-a-supervisor-of-your-choice">Launch daemons under supervision using "storm" script and a supervisor of your choice</h3>
+<h3 id="launch-daemons-under-supervision-using-"storm"-script-and-a-supervisor-of-your-choice">Launch daemons under supervision using "storm" script and a supervisor of your choice</h3>
<p>The last step is to launch all the Storm daemons. It is critical that you run each of these daemons under supervision. Storm is a <strong>fail-fast</strong> system which means the processes will halt whenever an unexpected error is encountered. Storm is designed so that it can safely halt at any point and recover correctly when the process is restarted. This is why Storm keeps no state in-process -- if Nimbus or the Supervisors restart, the running topologies are unaffected. Here's how to run the Storm daemons:</p>
@@ -272,7 +272,7 @@ The time to allow any given healthcheck
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Setting-up-development-environment.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Setting-up-development-environment.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Setting-up-development-environment.html (original)
+++ storm/site/publish/releases/current/Setting-up-development-environment.html Thu Apr 7 14:32:00 2016
@@ -137,7 +137,7 @@
<p>More detail on each of these steps is below.</p>
-<h3 id="what-is-a-development-environment">What is a development environment?</h3>
+<h3 id="what-is-a-development-environment?">What is a development environment?</h3>
<p>Storm has two modes of operation: local mode and remote mode. In local mode, you can develop and test topologies completely in process on your local machine. In remote mode, you submit topologies for execution on a cluster of machines.</p>
@@ -196,7 +196,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Spout-implementations.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Spout-implementations.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Spout-implementations.html (original)
+++ storm/site/publish/releases/current/Spout-implementations.html Thu Apr 7 14:32:00 2016
@@ -176,7 +176,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Structure-of-the-codebase.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Structure-of-the-codebase.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Structure-of-the-codebase.html (original)
+++ storm/site/publish/releases/current/Structure-of-the-codebase.html Thu Apr 7 14:32:00 2016
@@ -138,7 +138,7 @@
<p>The following sections explain each of these layers in more detail.</p>
-<h3 id="storm-thrift">storm.thrift</h3>
+<h3 id="storm.thrift">storm.thrift</h3>
<p>The first place to look to understand the structure of Storm's codebase is the <a href="http://github.com/apache/storm/blob/v0.10.0/storm-core/src/storm.thrift">storm.thrift</a> file.</p>
@@ -312,7 +312,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Support-for-non-java-languages.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Support-for-non-java-languages.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Support-for-non-java-languages.html (original)
+++ storm/site/publish/releases/current/Support-for-non-java-languages.html Thu Apr 7 14:32:00 2016
@@ -175,7 +175,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Transactional-topologies.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Transactional-topologies.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Transactional-topologies.html (original)
+++ storm/site/publish/releases/current/Transactional-topologies.html Thu Apr 7 14:32:00 2016
@@ -179,7 +179,7 @@
<p>After bolt 1 finishes its portion of the processing, it will be idle until the rest of the bolts finish and the next batch can be emitted from the spout.</p>
-<h3 id="design-3-storm-39-s-design">Design 3 (Storm's design)</h3>
+<h3 id="design-3-(storm's-design)">Design 3 (Storm's design)</h3>
<p>A key realization is that not all the work for processing batches of tuples needs to be strongly ordered. For example, when computing a global count, there's two parts to the computation:</p>
@@ -338,7 +338,7 @@
<li>BatchBolt's that are marked as committers: The only difference between this bolt and a regular batch bolt is when <code>finishBatch</code> is called. A committer bolt has <code>finishedBatch</code> called during the commit phase. The commit phase is guaranteed to occur only after all prior batches have successfully committed, and it will be retried until all bolts in the topology succeed the commit for the batch. There are two ways to make a <code>BatchBolt</code> a committer, by having the <code>BatchBolt</code> implement the <a href="javadocs/backtype/storm/transactional/ICommitter.html">ICommitter</a> marker interface, or by using the <code>setCommiterBolt</code> method in <code>TransactionalTopologyBuilder</code>.</li>
</ol>
-<h4 id="processing-phase-vs-commit-phase-in-bolts">Processing phase vs. commit phase in bolts</h4>
+<h4 id="processing-phase-vs.-commit-phase-in-bolts">Processing phase vs. commit phase in bolts</h4>
<p>To nail down the difference between the processing phase and commit phase of a transaction, let's look at an example topology:</p>
@@ -389,7 +389,7 @@
<li><em>Number of active batches permissible at once:</em> You must set a limit to the number of batches that can be processed at once. You configure this using the "topology.max.spout.pending" config. If you don't set this config, it will default to 1.</li>
</ol>
-<h2 id="what-if-you-can-39-t-emit-the-same-batch-of-tuples-for-a-given-transaction-id">What if you can't emit the same batch of tuples for a given transaction id?</h2>
+<h2 id="what-if-you-can't-emit-the-same-batch-of-tuples-for-a-given-transaction-id?">What if you can't emit the same batch of tuples for a given transaction id?</h2>
<p>So far the discussion around transactional topologies has assumed that you can always emit the exact same batch of tuples for the same transaction id. So what do you do if this is not possible?</p>
@@ -535,7 +535,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Trident-API-Overview.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Trident-API-Overview.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Trident-API-Overview.html (original)
+++ storm/site/publish/releases/current/Trident-API-Overview.html Thu Apr 7 14:32:00 2016
@@ -597,7 +597,7 @@ Partition 2:
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Trident-spouts.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Trident-spouts.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Trident-spouts.html (original)
+++ storm/site/publish/releases/current/Trident-spouts.html Thu Apr 7 14:32:00 2016
@@ -207,7 +207,7 @@
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>
Modified: storm/site/publish/releases/current/Trident-state.html
URL: http://svn.apache.org/viewvc/storm/site/publish/releases/current/Trident-state.html?rev=1738133&r1=1738132&r2=1738133&view=diff
==============================================================================
--- storm/site/publish/releases/current/Trident-state.html (original)
+++ storm/site/publish/releases/current/Trident-state.html Thu Apr 7 14:32:00 2016
@@ -440,7 +440,7 @@ apple => [count=10, txid=2]
<h5>First Look</h5>
<ul class="footer-list">
<li><a href="/releases/current/Rationale.html">Rationale</a></li>
- <li><a href="/releases/current/tutorial.html">Tutorial</a></li>
+ <li><a href="/releases/current/Tutorial.html">Tutorial</a></li>
<li><a href="/releases/current/Setting-up-development-environment.html">Setting up development environment</a></li>
<li><a href="/releases/current/Creating-a-new-Storm-project.html">Creating a new Storm project</a></li>
</ul>