You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by ka...@apache.org on 2015/10/03 06:33:38 UTC
svn commit: r1706521 - in /storm/site/publish: ./ 2012/08/02/ 2012/09/06/
2015/06/15/ contribute/ documentation/
Author: kabhwan
Date: Sat Oct 3 04:33:38 2015
New Revision: 1706521
URL: http://svn.apache.org/viewvc?rev=1706521&view=rev
Log:
reflect STORM-1033
Modified:
storm/site/publish/2012/08/02/storm080-released.html
storm/site/publish/2012/09/06/storm081-released.html
storm/site/publish/2015/06/15/storm0100-beta-released.html
storm/site/publish/contribute/BYLAWS.html
storm/site/publish/documentation/Acking-framework-implementation.html
storm/site/publish/documentation/Clojure-DSL.html
storm/site/publish/documentation/Common-patterns.html
storm/site/publish/documentation/Creating-a-new-Storm-project.html
storm/site/publish/documentation/FAQ.html
storm/site/publish/documentation/Fault-tolerance.html
storm/site/publish/documentation/Guaranteeing-message-processing.html
storm/site/publish/documentation/Home.html
storm/site/publish/documentation/Multilang-protocol.html
storm/site/publish/documentation/Setting-up-a-Storm-cluster.html
storm/site/publish/documentation/Setting-up-development-environment.html
storm/site/publish/documentation/Structure-of-the-codebase.html
storm/site/publish/documentation/Transactional-topologies.html
storm/site/publish/documentation/Troubleshooting.html
storm/site/publish/documentation/Understanding-the-parallelism-of-a-Storm-topology.html
storm/site/publish/documentation/flux.html
storm/site/publish/documentation/getting-help.html
storm/site/publish/documentation/storm-hbase.html
storm/site/publish/documentation/storm-hive.html
storm/site/publish/documentation/storm-jdbc.html
storm/site/publish/documentation/storm-redis.html
storm/site/publish/downloads.html
storm/site/publish/feed.xml
storm/site/publish/getting-help.html
Modified: storm/site/publish/2012/08/02/storm080-released.html
URL: http://svn.apache.org/viewvc/storm/site/publish/2012/08/02/storm080-released.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/2012/08/02/storm080-released.html (original)
+++ storm/site/publish/2012/08/02/storm080-released.html Sat Oct 3 04:33:38 2015
@@ -198,7 +198,7 @@ topology.transfer.buffer.size </p>
<p>These may require some tweaking to optimize your topologies, but most likely the default values will work fine for you out of the box. </p>
-<h2 id="decreased-zookeeper-load-/-increased-storm-ui-performance">Decreased Zookeeper load / increased Storm UI performance</h2>
+<h2 id="decreased-zookeeper-load-increased-storm-ui-performance">Decreased Zookeeper load / increased Storm UI performance</h2>
<p>Storm sends significantly less traffic to Zookeeper now (on the order of 10x less). Since it also uses so many fewer znodes to store state, the UI is significantly faster as well. </p>
Modified: storm/site/publish/2012/09/06/storm081-released.html
URL: http://svn.apache.org/viewvc/storm/site/publish/2012/09/06/storm081-released.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/2012/09/06/storm081-released.html (original)
+++ storm/site/publish/2012/09/06/storm081-released.html Sat Oct 3 04:33:38 2015
@@ -150,7 +150,7 @@
<div>
<p>Storm 0.8.1 is now available on the downloads page and in Maven. This release contains many bug fixes as well as a few important new features. These include: </p>
-<h2 id="storm's-unit-testing-facilities-have-been-exposed-via-java">Storm's unit testing facilities have been exposed via Java</h2>
+<h2 id="storm-39-s-unit-testing-facilities-have-been-exposed-via-java">Storm's unit testing facilities have been exposed via Java</h2>
<p>This is an extremely powerful API that lets you do things like:
a) Easily bring up and tear down local clusters
Modified: storm/site/publish/2015/06/15/storm0100-beta-released.html
URL: http://svn.apache.org/viewvc/storm/site/publish/2015/06/15/storm0100-beta-released.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/2015/06/15/storm0100-beta-released.html (original)
+++ storm/site/publish/2015/06/15/storm0100-beta-released.html Sat Oct 3 04:33:38 2015
@@ -152,7 +152,7 @@
<p>Aside from many stability and performance improvements, this release includes a number of important new features, some of which are highlighted below.</p>
-<h2 id="secure,-multi-tenant-deployment">Secure, Multi-Tenant Deployment</h2>
+<h2 id="secure-multi-tenant-deployment">Secure, Multi-Tenant Deployment</h2>
<p>Much like the early days of Hadoop, Apache Storm originally evolved in an environment where security was not a high-priority concern. Rather, it was assumed that Storm would be deployed to environments suitably cordoned off from security threats. While a large number of users were comfortable setting up their own security measures for Storm (usually at the Firewall/OS level), this proved a hindrance to broader adoption among larger enterprises where security policies prohibited deployment without specific safeguards.</p>
@@ -240,7 +240,7 @@ that allows users to stream data from St
<p>Further information can be found in the <a href="https://github.com/apache/storm/blob/v0.10.0-beta/external/storm-redis/README.md">storm-redis documentation</a>.</p>
-<h2 id="jdbc/rdbms-integration">JDBC/RDBMS Integration</h2>
+<h2 id="jdbc-rdbms-integration">JDBC/RDBMS Integration</h2>
<p>Many stream processing data flows require accessing data from or writing data to a relational data store. Storm 0.10.0 introduces highly flexible and customizable support for integrating with virtually any JDBC-compliant database.</p>
Modified: storm/site/publish/contribute/BYLAWS.html
URL: http://svn.apache.org/viewvc/storm/site/publish/contribute/BYLAWS.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/contribute/BYLAWS.html (original)
+++ storm/site/publish/contribute/BYLAWS.html Sat Oct 3 04:33:38 2015
@@ -94,17 +94,17 @@
<p>Apache projects define a set of roles with associated rights and responsibilities. These roles govern what tasks an individual may perform within the project. The roles are defined in the following sections:</p>
-<h3 id="users:">Users:</h3>
+<h3 id="users">Users:</h3>
<p>The most important participants in the project are people who use our software. The majority of our developers start out as users and guide their development efforts from the user's perspective.</p>
<p>Users contribute to the Apache projects by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apache community by helping other users on mailing lists and user support forums.</p>
-<h3 id="contributors:">Contributors:</h3>
+<h3 id="contributors">Contributors:</h3>
<p>Contributors are all of the volunteers who are contributing time, code, documentation, or resources to the Storm Project. A contributor that makes sustained, welcome contributions to the project may be invited to become a Committer, though the exact timing of such invitations depends on many factors.</p>
-<h3 id="committers:">Committers:</h3>
+<h3 id="committers">Committers:</h3>
<p>The project's Committers are responsible for the project's technical management. Committers have access to all project source repositories. Committers may cast binding votes on any technical discussion regarding storm.</p>
@@ -114,7 +114,7 @@
<p>A Committer who makes a sustained contribution to the project may be invited to become a member of the PMC. The form of contribution is not limited to code. It can also include code review, helping out users on the mailing lists, documentation, testing, etc.</p>
-<h3 id="project-management-committee(pmc):">Project Management Committee(PMC):</h3>
+<h3 id="project-management-committee-pmc">Project Management Committee(PMC):</h3>
<p>The PMC is responsible to the board and the ASF for the management and oversight of the Apache Storm codebase. The responsibilities of the PMC include:</p>
Modified: storm/site/publish/documentation/Acking-framework-implementation.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Acking-framework-implementation.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Acking-framework-implementation.html (original)
+++ storm/site/publish/documentation/Acking-framework-implementation.html Sat Oct 3 04:33:38 2015
@@ -94,7 +94,7 @@
<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>
-<h3 id="acker-execute()">acker <code>execute()</code></h3>
+<h3 id="acker-execute">acker <code>execute()</code></h3>
<p>The acker is actually a regular bolt, with its <a href="https://github.com/apache/storm/blob/46c3ba7/storm-core/src/clj/backtype/storm/daemon/acker.clj#L36">execute method</a> defined withing <code>mk-acker-bolt</code>. When a new tupletree is born, the spout sends the XORed edge-ids of each tuple recipient, which the acker records in its <code>pending</code> ledger. Every time an executor acks a tuple, the acker receives a partial checksum that is the XOR of the tuple's own edge-id (clearing it from the ledger) and the edge-id of each downstream tuple the executor emitted (thus entering them into the ledger).</p>
Modified: storm/site/publish/documentation/Clojure-DSL.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Clojure-DSL.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Clojure-DSL.html (original)
+++ storm/site/publish/documentation/Clojure-DSL.html Sat Oct 3 04:33:38 2015
@@ -245,7 +245,7 @@
</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>
Modified: storm/site/publish/documentation/Common-patterns.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Common-patterns.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Common-patterns.html (original)
+++ storm/site/publish/documentation/Common-patterns.html Sat Oct 3 04:33:38 2015
@@ -126,7 +126,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="/javadoc/apidocs/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="nf">ExpandUrl</span><span class="o">(),</span> <span class="n">parallelism</span><span class="o">)</span>
Modified: storm/site/publish/documentation/Creating-a-new-Storm-project.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Creating-a-new-Storm-project.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Creating-a-new-Storm-project.html (original)
+++ storm/site/publish/documentation/Creating-a-new-Storm-project.html Sat Oct 3 04:33:38 2015
@@ -105,7 +105,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>
Modified: storm/site/publish/documentation/FAQ.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/FAQ.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/FAQ.html (original)
+++ storm/site/publish/documentation/FAQ.html Sat Oct 3 04:33:38 2015
@@ -92,7 +92,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>
@@ -105,7 +105,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>
@@ -116,7 +116,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
@@ -130,7 +130,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>
@@ -146,7 +146,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>
@@ -163,23 +163,23 @@
<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's-metadata-record?">What can I store into the spout's metadata record?</h3>
+<h3 id="what-can-i-store-into-the-spout-39-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-'emitpartitionbatchnew'-function-called?">How often is the 'emitPartitionBatchNew' function called?</h3>
+<h3 id="how-often-is-the-39-emitpartitionbatchnew-39-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="https://github.com/apache/storm/blob/master/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="https://github.com/apache/storm/blob/master/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>
@@ -189,11 +189,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>
@@ -208,13 +208,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 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>
Modified: storm/site/publish/documentation/Fault-tolerance.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Fault-tolerance.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Fault-tolerance.html (original)
+++ storm/site/publish/documentation/Fault-tolerance.html Sat Oct 3 04:33:38 2015
@@ -92,27 +92,27 @@
<p>This page explains the design details of Storm that make it a fault-tolerant system.</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 reassign the worker to another machine.</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>
Modified: storm/site/publish/documentation/Guaranteeing-message-processing.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Guaranteeing-message-processing.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Guaranteeing-message-processing.html (original)
+++ storm/site/publish/documentation/Guaranteeing-message-processing.html Sat Oct 3 04:33:38 2015
@@ -92,7 +92,7 @@
<p>Storm guarantees that each message coming off a spout will be fully processed. This page describes how Storm accomplishes this guarantee and what you have to do as a user to benefit from Storm's reliability capabilities.</p>
-<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>
+<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>
<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="nf">TopologyBuilder</span><span class="o">();</span>
@@ -111,7 +111,7 @@
<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="/javadoc/apidocs/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="/javadoc/apidocs/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>
@@ -129,7 +129,7 @@
<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's-reliability-api?">What is Storm's reliability API?</h3>
+<h3 id="what-is-storm-39-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>
@@ -195,11 +195,11 @@
<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." Storm 0.7.0 introduced the "transactional topologies" feature, which enables you to get fully fault-tolerant exactly-once messaging semantics for most computations. Read more about transactional topologies <a href="Transactional-topologies.html">here</a>. </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 executors for a topology in the topology configuration using <a href="/javadoc/apidocs/backtype/storm/Config.html#TOPOLOGY_ACKER_EXECUTORS">Config.TOPOLOGY_ACKER_EXECUTORS</a>. Storm defaults TOPOLOGY_ACKER_EXECUTORS to be equal to the number of workers configured in the topology -- you will need to increase this number for topologies processing large amounts of messages.</p>
Modified: storm/site/publish/documentation/Home.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Home.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Home.html (original)
+++ storm/site/publish/documentation/Home.html Sat Oct 3 04:33:38 2015
@@ -130,13 +130,13 @@
<p>You can view the archives of the mailing list <a href="http://mail-archives.apache.org/mod_mbox/storm-dev/">here</a>.</p>
-<h4 id="which-list-should-i-send/subscribe-to?">Which list should I send/subscribe to?</h4>
+<h4 id="which-list-should-i-send-subscribe-to">Which list should I send/subscribe to?</h4>
<p>If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to <a href="user@storm.apache.org">user@storm.apache.org</a>. </p>
<p>If you are building storm from source, developing new features, or otherwise hacking storm source code, then <a href="dev@storm.apache.org">dev@storm.apache.org</a> is more appropriate. </p>
-<h4 id="what-will-happen-with-storm-user@googlegroups.com?">What will happen with <a href="mailto:storm-user@googlegroups.com">storm-user@googlegroups.com</a>?</h4>
+<h4 id="what-will-happen-with-storm-user-googlegroups-com">What will happen with <a href="mailto:storm-user@googlegroups.com">storm-user@googlegroups.com</a>?</h4>
<p>All existing messages will remain archived there, and can be accessed/searched <a href="https://groups.google.com/forum/#!forum/storm-user">here</a>.</p>
Modified: storm/site/publish/documentation/Multilang-protocol.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Multilang-protocol.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Multilang-protocol.html (original)
+++ storm/site/publish/documentation/Multilang-protocol.html Sat Oct 3 04:33:38 2015
@@ -321,7 +321,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
Modified: storm/site/publish/documentation/Setting-up-a-Storm-cluster.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Setting-up-a-Storm-cluster.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Setting-up-a-Storm-cluster.html (original)
+++ storm/site/publish/documentation/Setting-up-a-Storm-cluster.html Sat Oct 3 04:33:38 2015
@@ -130,7 +130,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="https://github.com/apache/storm/blob/master/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>
@@ -154,11 +154,11 @@
<span class="p-Indicator">-</span> <span class="l-Scalar-Plain">6702</span>
<span class="p-Indicator">-</span> <span class="l-Scalar-Plain">6703</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-"storm"-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-quot-storm-quot-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>
Modified: storm/site/publish/documentation/Setting-up-development-environment.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Setting-up-development-environment.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Setting-up-development-environment.html (original)
+++ storm/site/publish/documentation/Setting-up-development-environment.html Sat Oct 3 04:33:38 2015
@@ -99,7 +99,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>
Modified: storm/site/publish/documentation/Structure-of-the-codebase.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Structure-of-the-codebase.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Structure-of-the-codebase.html (original)
+++ storm/site/publish/documentation/Structure-of-the-codebase.html Sat Oct 3 04:33:38 2015
@@ -100,7 +100,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="https://github.com/apache/storm/blob/master/storm-core/src/storm.thrift">storm.thrift</a> file.</p>
Modified: storm/site/publish/documentation/Transactional-topologies.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Transactional-topologies.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Transactional-topologies.html (original)
+++ storm/site/publish/documentation/Transactional-topologies.html Sat Oct 3 04:33:38 2015
@@ -141,7 +141,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's-design)">Design 3 (Storm's design)</h3>
+<h3 id="design-3-storm-39-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>
@@ -300,7 +300,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="/javadoc/apidocs/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>
@@ -351,7 +351,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'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-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>
<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>
Modified: storm/site/publish/documentation/Troubleshooting.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Troubleshooting.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Troubleshooting.html (original)
+++ storm/site/publish/documentation/Troubleshooting.html Sat Oct 3 04:33:38 2015
@@ -157,7 +157,7 @@
<li>Try deleting the local dirs for the supervisors and restarting the daemons. Supervisors create a unique id for themselves and store it locally. When that id is copied to other nodes, Storm gets confused. </li>
</ul>
-<h3 id=""multiple-defaults.yaml-found"-error">"Multiple defaults.yaml found" error</h3>
+<h3 id="quot-multiple-defaults-yaml-found-quot-error">"Multiple defaults.yaml found" error</h3>
<p>Symptoms:</p>
@@ -171,7 +171,7 @@
<li>You're most likely including the Storm jars inside your topology jar. When packaging your topology jar, don't include the Storm jars as Storm will put those on the classpath for you.</li>
</ul>
-<h3 id=""nosuchmethoderror"-when-running-storm-jar">"NoSuchMethodError" when running storm jar</h3>
+<h3 id="quot-nosuchmethoderror-quot-when-running-storm-jar">"NoSuchMethodError" when running storm jar</h3>
<p>Symptoms:</p>
Modified: storm/site/publish/documentation/Understanding-the-parallelism-of-a-Storm-topology.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/Understanding-the-parallelism-of-a-Storm-topology.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/Understanding-the-parallelism-of-a-Storm-topology.html (original)
+++ storm/site/publish/documentation/Understanding-the-parallelism-of-a-Storm-topology.html Sat Oct 3 04:33:38 2015
@@ -90,7 +90,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>
+<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>
@@ -128,7 +128,7 @@
</ul></li>
</ul>
-<h3 id="number-of-executors-(threads)">Number of executors (threads)</h3>
+<h3 id="number-of-executors-threads">Number of executors (threads)</h3>
<ul>
<li>Description: How many executors to spawn <em>per component</em>.</li>
Modified: storm/site/publish/documentation/flux.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/flux.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/flux.html (original)
+++ storm/site/publish/documentation/flux.html Sat Oct 3 04:33:38 2015
@@ -167,10 +167,10 @@ on your system:</p>
<li>Node.js 0.10.x or later</li>
</ul>
-<h4 id="building-with-unit-tests-enabled:">Building with unit tests enabled:</h4>
+<h4 id="building-with-unit-tests-enabled">Building with unit tests enabled:</h4>
<div class="highlight"><pre><code class="language-text" data-lang="text">mvn clean install
</code></pre></div>
-<h4 id="building-with-unit-tests-disabled:">Building with unit tests disabled:</h4>
+<h4 id="building-with-unit-tests-disabled">Building with unit tests disabled:</h4>
<p>If you would like to build Flux without installing Python or Node.js you can simply skip the unit tests:</p>
<div class="highlight"><pre><code class="language-text" data-lang="text">mvn clean install -DskipTests=true
@@ -178,7 +178,7 @@ on your system:</p>
<p>Note that if you plan on using Flux to deploy topologies to a remote cluster, you will still need to have Python
installed since it is required by Apache Storm.</p>
-<h4 id="building-with-integration-tests-enabled:">Building with integration tests enabled:</h4>
+<h4 id="building-with-integration-tests-enabled">Building with integration tests enabled:</h4>
<div class="highlight"><pre><code class="language-text" data-lang="text">mvn clean install -DskipIntegration=false
</code></pre></div>
<h3 id="packaging-with-maven">Packaging with Maven</h3>
@@ -372,7 +372,7 @@ definition consists of the following:</p
<span class="l-Scalar-Plain">grouping</span><span class="p-Indicator">:</span>
<span class="l-Scalar-Plain">type</span><span class="p-Indicator">:</span> <span class="l-Scalar-Plain">SHUFFLE</span>
</code></pre></div>
-<h2 id="property-substitution/filtering">Property Substitution/Filtering</h2>
+<h2 id="property-substitution-filtering">Property Substitution/Filtering</h2>
<p>It's common for developers to want to easily switch between configurations, for example switching deployment between
a development environment and a production environment. This can be accomplished by using separate YAML configuration
@@ -397,7 +397,7 @@ if you invoked flux like so:</p>
</code></pre></div>
<p>In this case, Flux would replace <code>${kafka.zookeeper.hosts}</code> with <code>localhost:2181</code> before parsing the YAML contents.</p>
-<h3 id="environment-variable-substitution/filtering">Environment Variable Substitution/Filtering</h3>
+<h3 id="environment-variable-substitution-filtering">Environment Variable Substitution/Filtering</h3>
<p>Flux also allows environment variable substitution. For example, if an environment variable named <code>ZK_HOSTS</code> if defined,
you can reference it in a Flux YAML file with the following syntax:</p>
@@ -415,7 +415,7 @@ the following will make an instance of t
<span class="p-Indicator">-</span> <span class="l-Scalar-Plain">id</span><span class="p-Indicator">:</span> <span class="s">"stringScheme"</span>
<span class="l-Scalar-Plain">className</span><span class="p-Indicator">:</span> <span class="s">"storm.kafka.StringScheme"</span>
</code></pre></div>
-<h3 id="contructor-arguments,-references,-properties-and-configuration-methods">Contructor Arguments, References, Properties and Configuration Methods</h3>
+<h3 id="contructor-arguments-references-properties-and-configuration-methods">Contructor Arguments, References, Properties and Configuration Methods</h3>
<h4 id="constructor-arguments">Constructor Arguments</h4>
@@ -504,7 +504,7 @@ that use the builder pattern for configu
<p>Arguments passed to configuration methods work much the same way as constructor arguments, and support references as
well.</p>
-<h3 id="using-java-enums-in-contructor-arguments,-references,-properties-and-configuration-methods">Using Java <code>enum</code>s in Contructor Arguments, References, Properties and Configuration Methods</h3>
+<h3 id="using-java-enums-in-contructor-arguments-references-properties-and-configuration-methods">Using Java <code>enum</code>s in Contructor Arguments, References, Properties and Configuration Methods</h3>
<p>You can easily use Java <code>enum</code> values as arguments in a Flux YAML file, simply by referencing the name of the <code>enum</code>.</p>
@@ -819,7 +819,7 @@ same file. Includes may be either files,
<span class="l-Scalar-Plain">grouping</span><span class="p-Indicator">:</span>
<span class="l-Scalar-Plain">type</span><span class="p-Indicator">:</span> <span class="l-Scalar-Plain">SHUFFLE</span>
</code></pre></div>
-<h2 id="micro-batching-(trident)-api-support">Micro-Batching (Trident) API Support</h2>
+<h2 id="micro-batching-trident-api-support">Micro-Batching (Trident) API Support</h2>
<p>Currenty, the Flux YAML DSL only supports the Core Storm API, but support for Storm's micro-batching API is planned.</p>
Modified: storm/site/publish/documentation/getting-help.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/getting-help.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/getting-help.html (original)
+++ storm/site/publish/documentation/getting-help.html Sat Oct 3 04:33:38 2015
@@ -106,13 +106,13 @@
<p>You can view the archives of the mailing list <a href="http://mail-archives.apache.org/mod_mbox/storm-dev/">here</a>.</p>
-<h4 id="which-list-should-i-send/subscribe-to?">Which list should I send/subscribe to?</h4>
+<h4 id="which-list-should-i-send-subscribe-to">Which list should I send/subscribe to?</h4>
<p>If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to <a href="user@storm.apache.org">user@storm.apache.org</a>. </p>
<p>If you are building storm from source, developing new features, or otherwise hacking storm source code, then <a href="dev@storm.apache.org">dev@storm.apache.org</a> is more appropriate. </p>
-<h4 id="what-will-happen-with-storm-user@googlegroups.com?">What will happen with <a href="mailto:storm-user@googlegroups.com">storm-user@googlegroups.com</a>?</h4>
+<h4 id="what-will-happen-with-storm-user-googlegroups-com">What will happen with <a href="mailto:storm-user@googlegroups.com">storm-user@googlegroups.com</a>?</h4>
<p>All existing messages will remain archived there, and can be accessed/searched <a href="https://groups.google.com/forum/#!forum/storm-user">here</a>.</p>
Modified: storm/site/publish/documentation/storm-hbase.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/storm-hbase.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/storm-hbase.html (original)
+++ storm/site/publish/documentation/storm-hbase.html Sat Oct 3 04:33:38 2015
@@ -125,7 +125,7 @@ provided for the storm-hbase connector.
<span class="n">config</span><span class="o">.</span><span class="na">put</span><span class="o">(</span><span class="s">"storm.kerberos.principal"</span><span class="o">,</span> <span class="s">"$principle"</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">"$topologyName"</span><span class="o">,</span> <span class="n">config</span><span class="o">,</span> <span class="n">builder</span><span class="o">.</span><span class="na">createTopology</span><span class="o">());</span>
</code></pre></div>
-<h2 id="working-with-secure-hbase-using-delegation-tokens.">Working with Secure HBASE using delegation tokens.</h2>
+<h2 id="working-with-secure-hbase-using-delegation-tokens">Working with Secure HBASE using delegation tokens.</h2>
<p>If your topology is going to interact with secure HBase, your bolts/states needs to be authenticated by HBase.
The approach described above requires that all potential worker hosts have "storm.keytab.file" on them. If you have
@@ -238,7 +238,7 @@ values to be emitted by the bolt.</p>
<p>You can look at an example topology LookupWordCount.java under <code>src/test/java</code>.</p>
-<h2 id="example:-persistent-word-count">Example: Persistent Word Count</h2>
+<h2 id="example-persistent-word-count">Example: Persistent Word Count</h2>
<p>A runnable example can be found in the <code>src/test/java</code> directory.</p>
Modified: storm/site/publish/documentation/storm-hive.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/storm-hive.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/storm-hive.html (original)
+++ storm/site/publish/documentation/storm-hive.html Sat Oct 3 04:33:38 2015
@@ -99,7 +99,7 @@
To use Hive streaming API users need to create a bucketed table with ORC format. Example below</p>
<div class="highlight"><pre><code class="language-sql" data-lang="sql"> <span class="k">create</span> <span class="k">table</span> <span class="n">test_table</span> <span class="p">(</span> <span class="n">id</span> <span class="nb">INT</span><span class="p">,</span> <span class="n">name</span> <span class="n">STRING</span><span class="p">,</span> <span class="n">phone</span> <span class="n">STRING</span><span class="p">,</span> <span class="n">street</span> <span class="n">STRING</span><span class="p">)</span> <span class="n">partitioned</span> <span class="k">by</span> <span class="p">(</span><span class="n">city</span> <span class="n">STRING</span><span class="p">,</span> <span class="k">state</span> <span class="n">STRING</span><span class="p">)</span> <span class="n">stored</span> <span class="k">as</span> <span class="n">orc</span> <span class="n">tblproperties</span> <span class="p">(</span><span class="ss">"orc.compress"</span><span class="o">=</span><span class="
ss">"NONE"</span><span class="p">);</span>
</code></pre></div>
-<h2 id="hivebolt-(org.apache.storm.hive.bolt.hivebolt)">HiveBolt (org.apache.storm.hive.bolt.HiveBolt)</h2>
+<h2 id="hivebolt-org-apache-storm-hive-bolt-hivebolt">HiveBolt (org.apache.storm.hive.bolt.HiveBolt)</h2>
<p>HiveBolt streams tuples directly into Hive. Tuples are written using Hive Transactions.
Partitions to which HiveBolt will stream to can either created or pre-created or optionally
@@ -151,7 +151,7 @@ User should make sure that Tuple field n
</tr>
</tbody></table>
-<h3 id="hiveoptions-(org.apache.storm.hive.common.hiveoptions)">HiveOptions (org.apache.storm.hive.common.HiveOptions)</h3>
+<h3 id="hiveoptions-org-apache-storm-hive-common-hiveoptions">HiveOptions (org.apache.storm.hive.common.HiveOptions)</h3>
<p>HiveBolt takes in HiveOptions as a constructor arg.</p>
<div class="highlight"><pre><code class="language-java" data-lang="java"> <span class="n">HiveOptions</span> <span class="n">hiveOptions</span> <span class="o">=</span> <span class="k">new</span> <span class="nf">HiveOptions</span><span class="o">(</span><span class="n">metaStoreURI</span><span class="o">,</span><span class="n">dbName</span><span class="o">,</span><span class="n">tblName</span><span class="o">,</span><span class="n">mapper</span><span class="o">)</span>
@@ -235,7 +235,7 @@ User should make sure that Tuple field n
</tr>
</tbody></table>
-<h2 id="hivestate-(org.apache.storm.hive.trident.hivetrident)">HiveState (org.apache.storm.hive.trident.HiveTrident)</h2>
+<h2 id="hivestate-org-apache-storm-hive-trident-hivetrident">HiveState (org.apache.storm.hive.trident.HiveTrident)</h2>
<p>Hive Trident state also follows similar pattern to HiveBolt it takes in HiveOptions as an arg.</p>
<div class="highlight"><pre><code class="language-java" data-lang="java"> <span class="n">DelimitedRecordHiveMapper</span> <span class="n">mapper</span> <span class="o">=</span> <span class="k">new</span> <span class="nf">DelimitedRecordHiveMapper</span><span class="o">()</span>
Modified: storm/site/publish/documentation/storm-jdbc.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/storm-jdbc.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/storm-jdbc.html (original)
+++ storm/site/publish/documentation/storm-jdbc.html Sat Oct 3 04:33:38 2015
@@ -96,7 +96,7 @@ in a storm topology.</p>
<p><strong>Note</strong>: Throughout the examples below, we make use of com.google.common.collect.Lists and com.google.common.collect.Maps.</p>
-<h2 id="inserting-into-a-database.">Inserting into a database.</h2>
+<h2 id="inserting-into-a-database">Inserting into a database.</h2>
<p>The bolt and trident state included in this package for inserting data into a database tables are tied to a single table.</p>
@@ -288,7 +288,7 @@ The default is set to value of topology.
<span class="o">.</span><span class="na">withSelectQuery</span><span class="o">(</span><span class="s">"select user_name from user_details where user_id = ?"</span><span class="o">);</span>
<span class="o">.</span><span class="na">withQueryTimeoutSecs</span><span class="o">(</span><span class="mi">30</span><span class="o">);</span>
</code></pre></div>
-<h2 id="example:">Example:</h2>
+<h2 id="example">Example:</h2>
<p>A runnable example can be found in the <code>src/test/java/topology</code> directory.</p>
Modified: storm/site/publish/documentation/storm-redis.html
URL: http://svn.apache.org/viewvc/storm/site/publish/documentation/storm-redis.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/documentation/storm-redis.html (original)
+++ storm/site/publish/documentation/storm-redis.html Sat Oct 3 04:33:38 2015
@@ -96,7 +96,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>
Modified: storm/site/publish/downloads.html
URL: http://svn.apache.org/viewvc/storm/site/publish/downloads.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/downloads.html (original)
+++ storm/site/publish/downloads.html Sat Oct 3 04:33:38 2015
@@ -103,22 +103,22 @@
The list of changes for this release can be found <a href="https://github.com/apache/storm/blob/v0.10.0-beta1/CHANGELOG.md">here.</a>
<ul>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz">apache-storm-0.10.0-beta1.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz">apache-storm-0.10.0-beta1.tar.gz</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip">apache-storm-0.10.0-beta1.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip">apache-storm-0.10.0-beta1.zip</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1.zip.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz">apache-storm-0.10.0-beta1-src.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz">apache-storm-0.10.0-beta1-src.tar.gz</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip">apache-storm-0.10.0-beta1-src.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip">apache-storm-0.10.0-beta1-src.zip</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.10.0-beta1/apache-storm-0.10.0-beta1-src.zip.md5">MD5</a>]
@@ -132,22 +132,22 @@
The list of changes for this release can be found <a href="https://github.com/apache/storm/blob/v0.9.5/CHANGELOG.md">here.</a>
<ul>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.5/apache-storm-0.9.5.tar.gz">apache-storm-0.9.5.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.5/apache-storm-0.9.5.tar.gz">apache-storm-0.9.5.tar.gz</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5.tar.gz.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5.tar.gz.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.5/apache-storm-0.9.5.zip">apache-storm-0.9.5.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.5/apache-storm-0.9.5.zip">apache-storm-0.9.5.zip</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5.zip.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5.zip.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5.zip.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.tar.gz">apache-storm-0.9.5-src.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.tar.gz">apache-storm-0.9.5-src.tar.gz</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.tar.gz.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.tar.gz.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.zip">apache-storm-0.9.5-src.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.zip">apache-storm-0.9.5-src.zip</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.zip.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.zip.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.5/apache-storm-0.9.5-src.zip.md5">MD5</a>]
@@ -172,22 +172,22 @@ version: 0.9.5</pre>
<b>0.9.4</b>
<ul>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.4/apache-storm-0.9.4.tar.gz">apache-storm-0.9.4.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.4/apache-storm-0.9.4.tar.gz">apache-storm-0.9.4.tar.gz</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4.tar.gz.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4.tar.gz.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.4/apache-storm-0.9.4.zip">apache-storm-0.9.4.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.4/apache-storm-0.9.4.zip">apache-storm-0.9.4.zip</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4.zip.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4.zip.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4.zip.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.tar.gz">apache-storm-0.9.4-src.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.tar.gz">apache-storm-0.9.4-src.tar.gz</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.tar.gz.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.tar.gz.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.zip">apache-storm-0.9.4-src.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.zip">apache-storm-0.9.4-src.zip</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.zip.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.zip.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.4/apache-storm-0.9.4-src.zip.md5">MD5</a>]
@@ -197,22 +197,22 @@ version: 0.9.5</pre>
<b>0.9.3</b>
<ul>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.3/apache-storm-0.9.3.tar.gz">apache-storm-0.9.3.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.3/apache-storm-0.9.3.tar.gz">apache-storm-0.9.3.tar.gz</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3.tar.gz.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3.tar.gz.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.3/apache-storm-0.9.3.zip">apache-storm-0.9.3.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.3/apache-storm-0.9.3.zip">apache-storm-0.9.3.zip</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3.zip.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3.zip.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3.zip.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.tar.gz">apache-storm-0.9.3-src.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.tar.gz">apache-storm-0.9.3-src.tar.gz</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.tar.gz.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.tar.gz.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.zip">apache-storm-0.9.3-src.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.zip">apache-storm-0.9.3-src.zip</a>
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.zip.asc">PGP</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.zip.sha">SHA512</a>]
[<a href="http://www.us.apache.org/dist/storm/apache-storm-0.9.3/apache-storm-0.9.3-src.zip.md5">MD5</a>]
@@ -223,22 +223,22 @@ version: 0.9.5</pre>
<b>0.9.2-incubating</b>
<ul>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.tar.gz">apache-storm-0.9.2-incubating.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.tar.gz">apache-storm-0.9.2-incubating.tar.gz</a>
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.tar.gz.asc">PGP</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.tar.gz.sha">SHA512</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.zip">apache-storm-0.9.2-incubating.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.zip">apache-storm-0.9.2-incubating.zip</a>
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.zip.asc">PGP</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.zip.sha">SHA512</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating.zip.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz">apache-storm-0.9.2-incubating-src.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz">apache-storm-0.9.2-incubating-src.tar.gz</a>
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz.asc">PGP</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz.sha">SHA512</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.zip">apache-storm-0.9.2-incubating-src.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.zip">apache-storm-0.9.2-incubating-src.zip</a>
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.zip.asc">PGP</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.zip.sha">SHA512</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.zip.md5">MD5</a>]
@@ -249,22 +249,22 @@ version: 0.9.5</pre>
<b>0.9.1-incubating</b>
<ul>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.tar.gz">apache-storm-0.9.1-incubating.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.tar.gz">apache-storm-0.9.1-incubating.tar.gz</a>
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.tar.gz.asc">PGP</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.tar.gz.sha">SHA512</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.zip">apache-storm-0.9.1-incubating.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.zip">apache-storm-0.9.1-incubating.zip</a>
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.zip.asc">PGP</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.zip.sha">SHA512</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating.zip.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.tar.gz">apache-storm-0.9.1-incubating-src.tar.gz</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.tar.gz">apache-storm-0.9.1-incubating-src.tar.gz</a>
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.tar.gz.asc">PGP</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.tar.gz.sha">SHA512</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.tar.gz.md5">MD5</a>]
</li>
- <li><a href="http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.zip">apache-storm-0.9.1-incubating-src.zip</a>
+ <li><a href="http://www.apache.org/dyn/closer.lua/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.zip">apache-storm-0.9.1-incubating-src.zip</a>
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.zip.asc">PGP</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.zip.sha">SHA512</a>]
[<a href="http://www.apache.org/dist/storm/apache-storm-0.9.1-incubating/apache-storm-0.9.1-incubating-src.zip.md5">MD5</a>]
Modified: storm/site/publish/feed.xml
URL: http://svn.apache.org/viewvc/storm/site/publish/feed.xml?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/feed.xml (original)
+++ storm/site/publish/feed.xml Sat Oct 3 04:33:38 2015
@@ -5,8 +5,8 @@
<description></description>
<link>http://storm.apache.org/</link>
<atom:link href="http://storm.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Tue, 29 Sep 2015 15:26:07 -0400</pubDate>
- <lastBuildDate>Tue, 29 Sep 2015 15:26:07 -0400</lastBuildDate>
+ <pubDate>Sat, 03 Oct 2015 13:31:05 +0900</pubDate>
+ <lastBuildDate>Sat, 03 Oct 2015 13:31:05 +0900</lastBuildDate>
<generator>Jekyll v2.5.3</generator>
<item>
@@ -15,7 +15,7 @@
<p>Aside from many stability and performance improvements, this release includes a number of important new features, some of which are highlighted below.</p>
-<h2 id="secure,-multi-tenant-deployment">Secure, Multi-Tenant Deployment</h2>
+<h2 id="secure-multi-tenant-deployment">Secure, Multi-Tenant Deployment</h2>
<p>Much like the early days of Hadoop, Apache Storm originally evolved in an environment where security was not a high-priority concern. Rather, it was assumed that Storm would be deployed to environments suitably cordoned off from security threats. While a large number of users were comfortable setting up their own security measures for Storm (usually at the Firewall/OS level), this proved a hindrance to broader adoption among larger enterprises where security policies prohibited deployment without specific safeguards.</p>
@@ -103,7 +103,7 @@ that allows users to stream data from St
<p>Further information can be found in the <a href="https://github.com/apache/storm/blob/v0.10.0-beta/external/storm-redis/README.md">storm-redis documentation</a>.</p>
-<h2 id="jdbc/rdbms-integration">JDBC/RDBMS Integration</h2>
+<h2 id="jdbc-rdbms-integration">JDBC/RDBMS Integration</h2>
<p>Many stream processing data flows require accessing data from or writing data to a relational data store. Storm 0.10.0 introduces highly flexible and customizable support for integrating with virtually any JDBC-compliant database.</p>
@@ -296,7 +296,7 @@ that allows users to stream data from St
<li>STORM-130: Supervisor getting killed due to java.io.FileNotFoundException: File &#39;../stormconf.ser&#39; does not exist.</li>
</ul>
</description>
- <pubDate>Mon, 15 Jun 2015 00:00:00 -0400</pubDate>
+ <pubDate>Mon, 15 Jun 2015 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2015/06/15/storm0100-beta-released.html</link>
<guid isPermaLink="true">http://storm.apache.org/2015/06/15/storm0100-beta-released.html</guid>
@@ -322,7 +322,7 @@ that allows users to stream data from St
<li>STORM-130: Supervisor getting killed due to java.io.FileNotFoundException: File &#39;../stormconf.ser&#39; does not exist.</li>
</ul>
</description>
- <pubDate>Thu, 04 Jun 2015 00:00:00 -0400</pubDate>
+ <pubDate>Thu, 04 Jun 2015 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2015/06/04/storm095-released.html</link>
<guid isPermaLink="true">http://storm.apache.org/2015/06/04/storm095-released.html</guid>
@@ -349,7 +349,7 @@ that allows users to stream data from St
<li>STORM-130: Supervisor getting killed due to java.io.FileNotFoundException: File &#39;../stormconf.ser&#39; does not exist.</li>
</ul>
</description>
- <pubDate>Wed, 25 Mar 2015 00:00:00 -0400</pubDate>
+ <pubDate>Wed, 25 Mar 2015 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2015/03/25/storm094-released.html</link>
<guid isPermaLink="true">http://storm.apache.org/2015/03/25/storm094-released.html</guid>
@@ -545,7 +545,7 @@ that allows users to stream data from St
<li>STORM-514: Update storm-starter README now that Storm has graduated from Incubator</li>
</ul>
</description>
- <pubDate>Tue, 25 Nov 2014 00:00:00 -0500</pubDate>
+ <pubDate>Tue, 25 Nov 2014 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2014/11/25/storm093-released.html</link>
<guid isPermaLink="true">http://storm.apache.org/2014/11/25/storm093-released.html</guid>
@@ -560,7 +560,7 @@ that allows users to stream data from St
<p>We heartily encourage you to <a href="http://storm.apache.org/downloads.html">test the 0.9.3 release candidate</a> and provide your feedback regarding any issues via <a href="http://storm.apache.org/community.html">our mailing lists</a>, which is an easy and valuable way to contribute back to the Storm community and to help us moving to an official 0.9.3 release. You can find the <a href="http://storm.apache.org/downloads.html">0.9.3 release candidate in our Downloads section</a>.</p>
</description>
- <pubDate>Mon, 20 Oct 2014 00:00:00 -0400</pubDate>
+ <pubDate>Mon, 20 Oct 2014 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2014/10/20/storm093-release-candidate.html</link>
<guid isPermaLink="true">http://storm.apache.org/2014/10/20/storm093-release-candidate.html</guid>
@@ -695,7 +695,7 @@ version: 0.9.2-incubating
<li>STORM-146: Unit test regression when storm is compiled with 3.4.5 zookeeper</li>
</ul>
</description>
- <pubDate>Wed, 25 Jun 2014 00:00:00 -0400</pubDate>
+ <pubDate>Wed, 25 Jun 2014 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2014/06/25/storm092-released.html</link>
<guid isPermaLink="true">http://storm.apache.org/2014/06/25/storm092-released.html</guid>
@@ -742,7 +742,7 @@ version: 0.9.2-incubating
</tr>
</tbody></table>
</description>
- <pubDate>Tue, 17 Jun 2014 00:00:00 -0400</pubDate>
+ <pubDate>Tue, 17 Jun 2014 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2014/06/17/contest-results.html</link>
<guid isPermaLink="true">http://storm.apache.org/2014/06/17/contest-results.html</guid>
@@ -820,7 +820,7 @@ version: 0.9.2-incubating
<p>The authors of the selected Apache Storm logo(s) will be required to donate them to the Apache Storm project and complete and <a href="http://www.apache.org/licenses/icla.txt">Apache Individual Contributor License Agreement(ICLA)</a></p>
</description>
- <pubDate>Thu, 10 Apr 2014 00:00:00 -0400</pubDate>
+ <pubDate>Thu, 10 Apr 2014 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2014/04/10/storm-logo-contest.html</link>
<guid isPermaLink="true">http://storm.apache.org/2014/04/10/storm-logo-contest.html</guid>
@@ -936,7 +936,7 @@ storm.messaging.netty.min_wait_ms: 100
<li>Bug fix: Set component-specific configs correctly for Trident spouts</li>
</ul>
</description>
- <pubDate>Sun, 08 Dec 2013 00:00:00 -0500</pubDate>
+ <pubDate>Sun, 08 Dec 2013 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2013/12/08/storm090-released.html</link>
<guid isPermaLink="true">http://storm.apache.org/2013/12/08/storm090-released.html</guid>
@@ -1015,7 +1015,7 @@ storm.messaging.netty.min_wait_ms: 100
<li>Bug fix: Fix occasional cascading worker crashes due when a worker dies due to not removing connections from connection cache appropriately</li>
</ul>
</description>
- <pubDate>Fri, 11 Jan 2013 00:00:00 -0500</pubDate>
+ <pubDate>Fri, 11 Jan 2013 00:00:00 +0900</pubDate>
<link>http://storm.apache.org/2013/01/11/storm082-released.html</link>
<guid isPermaLink="true">http://storm.apache.org/2013/01/11/storm082-released.html</guid>
Modified: storm/site/publish/getting-help.html
URL: http://svn.apache.org/viewvc/storm/site/publish/getting-help.html?rev=1706521&r1=1706520&r2=1706521&view=diff
==============================================================================
--- storm/site/publish/getting-help.html (original)
+++ storm/site/publish/getting-help.html Sat Oct 3 04:33:38 2015
@@ -104,13 +104,13 @@
<p>You can view the archives of the mailing list <a href="http://mail-archives.apache.org/mod_mbox/storm-dev/">here</a>.</p>
-<h4 id="which-list-should-i-send/subscribe-to?">Which list should I send/subscribe to?</h4>
+<h4 id="which-list-should-i-send-subscribe-to">Which list should I send/subscribe to?</h4>
<p>If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to <a href="user@storm.apache.org">user@storm.apache.org</a>. </p>
<p>If you are building storm from source, developing new features, or otherwise hacking storm source code, then <a href="dev@storm.apache.org">dev@storm.apache.org</a> is more appropriate. </p>
-<h4 id="what-will-happen-with-storm-user@googlegroups.com?">What will happen with <a href="mailto:storm-user@googlegroups.com">storm-user@googlegroups.com</a>?</h4>
+<h4 id="what-will-happen-with-storm-user-googlegroups-com">What will happen with <a href="mailto:storm-user@googlegroups.com">storm-user@googlegroups.com</a>?</h4>
<p>All existing messages will remain archived there, and can be accessed/searched <a href="https://groups.google.com/forum/#!forum/storm-user">here</a>.</p>