You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by sr...@apache.org on 2018/05/15 15:21:02 UTC
[9/9] storm-site git commit: Rebuild site
Rebuild site
Project: http://git-wip-us.apache.org/repos/asf/storm-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm-site/commit/df5612be
Tree: http://git-wip-us.apache.org/repos/asf/storm-site/tree/df5612be
Diff: http://git-wip-us.apache.org/repos/asf/storm-site/diff/df5612be
Branch: refs/heads/asf-site
Commit: df5612be88aee245a21ee08ea6c41cd02dfd54d5
Parents: b9737c2
Author: Stig Rohde Døssing <st...@gmail.com>
Authored: Tue May 15 17:20:24 2018 +0200
Committer: Stig Rohde Døssing <st...@gmail.com>
Committed: Tue May 15 17:20:24 2018 +0200
----------------------------------------------------------------------
content/Powered-By.html | 4 ++--
content/contribute/BYLAWS.html | 4 ++--
content/contribute/Contributing-to-Storm.html | 4 ++--
content/contribute/People.html | 4 ++--
content/css/style.css | 12 ++++++++++++
content/feed.xml | 4 ++--
content/news.html | 4 ++--
.../releases/1.0.6/Acking-framework-implementation.html | 4 ++--
content/releases/1.0.6/Clojure-DSL.html | 4 ++--
content/releases/1.0.6/Command-line-client.html | 4 ++--
content/releases/1.0.6/Common-patterns.html | 4 ++--
content/releases/1.0.6/Concepts.html | 4 ++--
content/releases/1.0.6/Configuration.html | 4 ++--
content/releases/1.0.6/Contributing-to-Storm.html | 4 ++--
.../releases/1.0.6/Creating-a-new-Storm-project.html | 4 ++--
content/releases/1.0.6/DSLs-and-multilang-adapters.html | 4 ++--
content/releases/1.0.6/Daemon-Fault-Tolerance.html | 4 ++--
.../Defining-a-non-jvm-language-dsl-for-storm.html | 4 ++--
content/releases/1.0.6/Distributed-RPC.html | 4 ++--
content/releases/1.0.6/Eventlogging.html | 4 ++--
content/releases/1.0.6/FAQ.html | 4 ++--
content/releases/1.0.6/Fault-tolerance.html | 4 ++--
.../releases/1.0.6/Guaranteeing-message-processing.html | 4 ++--
content/releases/1.0.6/Hooks.html | 4 ++--
content/releases/1.0.6/Implementation-docs.html | 4 ++--
.../releases/1.0.6/Installing-native-dependencies.html | 4 ++--
content/releases/1.0.6/Kestrel-and-Storm.html | 4 ++--
content/releases/1.0.6/Lifecycle-of-a-topology.html | 4 ++--
content/releases/1.0.6/Local-mode.html | 4 ++--
content/releases/1.0.6/Logs.html | 4 ++--
content/releases/1.0.6/Maven.html | 4 ++--
.../releases/1.0.6/Message-passing-implementation.html | 4 ++--
content/releases/1.0.6/Metrics.html | 4 ++--
content/releases/1.0.6/Multilang-protocol.html | 4 ++--
content/releases/1.0.6/Pacemaker.html | 4 ++--
content/releases/1.0.6/Powered-By.html | 4 ++--
content/releases/1.0.6/Project-ideas.html | 4 ++--
content/releases/1.0.6/Rationale.html | 4 ++--
.../1.0.6/Resource_Aware_Scheduler_overview.html | 4 ++--
.../Running-topologies-on-a-production-cluster.html | 4 ++--
content/releases/1.0.6/SECURITY.html | 4 ++--
content/releases/1.0.6/STORM-UI-REST-API.html | 4 ++--
.../releases/1.0.6/Serialization-(prior-to-0.6.0).html | 4 ++--
content/releases/1.0.6/Serialization.html | 4 ++--
content/releases/1.0.6/Serializers.html | 4 ++--
content/releases/1.0.6/Setting-up-a-Storm-cluster.html | 4 ++--
.../1.0.6/Setting-up-development-environment.html | 4 ++--
content/releases/1.0.6/Spout-implementations.html | 4 ++--
content/releases/1.0.6/State-checkpointing.html | 4 ++--
content/releases/1.0.6/Storm-Scheduler.html | 4 ++--
...ti-language-protocol-(versions-0.7.0-and-below).html | 4 ++--
content/releases/1.0.6/Structure-of-the-codebase.html | 4 ++--
.../releases/1.0.6/Support-for-non-java-languages.html | 4 ++--
content/releases/1.0.6/Transactional-topologies.html | 4 ++--
content/releases/1.0.6/Trident-API-Overview.html | 4 ++--
content/releases/1.0.6/Trident-RAS-API.html | 4 ++--
content/releases/1.0.6/Trident-spouts.html | 4 ++--
content/releases/1.0.6/Trident-state.html | 4 ++--
content/releases/1.0.6/Trident-tutorial.html | 4 ++--
content/releases/1.0.6/Troubleshooting.html | 4 ++--
content/releases/1.0.6/Tutorial.html | 4 ++--
...derstanding-the-parallelism-of-a-Storm-topology.html | 4 ++--
.../1.0.6/Using-non-JVM-languages-with-Storm.html | 4 ++--
content/releases/1.0.6/Windowing.html | 4 ++--
content/releases/1.0.6/distcache-blobstore.html | 4 ++--
content/releases/1.0.6/dynamic-log-level-settings.html | 4 ++--
content/releases/1.0.6/dynamic-worker-profiling.html | 4 ++--
content/releases/1.0.6/flux.html | 4 ++--
content/releases/1.0.6/index.html | 4 ++--
content/releases/1.0.6/nimbus-ha-design.html | 4 ++--
content/releases/1.0.6/storm-cassandra.html | 4 ++--
content/releases/1.0.6/storm-elasticsearch.html | 4 ++--
content/releases/1.0.6/storm-eventhubs.html | 4 ++--
content/releases/1.0.6/storm-hbase.html | 4 ++--
content/releases/1.0.6/storm-hdfs.html | 4 ++--
content/releases/1.0.6/storm-hive.html | 4 ++--
content/releases/1.0.6/storm-jdbc.html | 4 ++--
content/releases/1.0.6/storm-jms-example.html | 4 ++--
content/releases/1.0.6/storm-jms-spring.html | 4 ++--
content/releases/1.0.6/storm-jms.html | 4 ++--
content/releases/1.0.6/storm-kafka-client.html | 4 ++--
content/releases/1.0.6/storm-kafka.html | 4 ++--
.../1.0.6/storm-metrics-profiling-internal-actions.html | 4 ++--
content/releases/1.0.6/storm-mongodb.html | 4 ++--
content/releases/1.0.6/storm-mqtt.html | 4 ++--
content/releases/1.0.6/storm-redis.html | 4 ++--
content/releases/1.0.6/storm-solr.html | 4 ++--
content/releases/1.0.6/storm-sql-internal.html | 4 ++--
content/releases/1.0.6/storm-sql.html | 4 ++--
content/releases/1.0.6/windows-users-guide.html | 4 ++--
.../releases/1.1.2/Acking-framework-implementation.html | 4 ++--
content/releases/1.1.2/Clojure-DSL.html | 4 ++--
content/releases/1.1.2/Command-line-client.html | 4 ++--
content/releases/1.1.2/Common-patterns.html | 4 ++--
content/releases/1.1.2/Concepts.html | 4 ++--
content/releases/1.1.2/Configuration.html | 4 ++--
content/releases/1.1.2/Contributing-to-Storm.html | 4 ++--
.../releases/1.1.2/Creating-a-new-Storm-project.html | 4 ++--
content/releases/1.1.2/DSLs-and-multilang-adapters.html | 4 ++--
content/releases/1.1.2/Daemon-Fault-Tolerance.html | 4 ++--
.../Defining-a-non-jvm-language-dsl-for-storm.html | 4 ++--
content/releases/1.1.2/Distributed-RPC.html | 4 ++--
content/releases/1.1.2/Eventlogging.html | 4 ++--
content/releases/1.1.2/FAQ.html | 4 ++--
content/releases/1.1.2/Fault-tolerance.html | 4 ++--
.../releases/1.1.2/Guaranteeing-message-processing.html | 4 ++--
content/releases/1.1.2/Hooks.html | 4 ++--
content/releases/1.1.2/Implementation-docs.html | 4 ++--
.../releases/1.1.2/Installing-native-dependencies.html | 4 ++--
content/releases/1.1.2/Joins.html | 4 ++--
content/releases/1.1.2/Kestrel-and-Storm.html | 4 ++--
content/releases/1.1.2/Lifecycle-of-a-topology.html | 4 ++--
content/releases/1.1.2/Local-mode.html | 4 ++--
content/releases/1.1.2/Logs.html | 4 ++--
content/releases/1.1.2/Maven.html | 4 ++--
.../releases/1.1.2/Message-passing-implementation.html | 4 ++--
content/releases/1.1.2/Metrics.html | 4 ++--
content/releases/1.1.2/Multilang-protocol.html | 4 ++--
content/releases/1.1.2/Pacemaker.html | 4 ++--
content/releases/1.1.2/Powered-By.html | 4 ++--
content/releases/1.1.2/Project-ideas.html | 4 ++--
content/releases/1.1.2/Rationale.html | 4 ++--
.../1.1.2/Resource_Aware_Scheduler_overview.html | 4 ++--
.../Running-topologies-on-a-production-cluster.html | 4 ++--
content/releases/1.1.2/SECURITY.html | 4 ++--
content/releases/1.1.2/STORM-UI-REST-API.html | 4 ++--
.../releases/1.1.2/Serialization-(prior-to-0.6.0).html | 4 ++--
content/releases/1.1.2/Serialization.html | 4 ++--
content/releases/1.1.2/Serializers.html | 4 ++--
content/releases/1.1.2/Setting-up-a-Storm-cluster.html | 4 ++--
.../1.1.2/Setting-up-development-environment.html | 4 ++--
content/releases/1.1.2/Spout-implementations.html | 4 ++--
content/releases/1.1.2/State-checkpointing.html | 4 ++--
content/releases/1.1.2/Storm-Scheduler.html | 4 ++--
...ti-language-protocol-(versions-0.7.0-and-below).html | 4 ++--
content/releases/1.1.2/Structure-of-the-codebase.html | 4 ++--
.../releases/1.1.2/Support-for-non-java-languages.html | 4 ++--
content/releases/1.1.2/Transactional-topologies.html | 4 ++--
content/releases/1.1.2/Trident-API-Overview.html | 4 ++--
content/releases/1.1.2/Trident-RAS-API.html | 4 ++--
content/releases/1.1.2/Trident-spouts.html | 4 ++--
content/releases/1.1.2/Trident-state.html | 4 ++--
content/releases/1.1.2/Trident-tutorial.html | 4 ++--
content/releases/1.1.2/Troubleshooting.html | 4 ++--
content/releases/1.1.2/Tutorial.html | 4 ++--
...derstanding-the-parallelism-of-a-Storm-topology.html | 4 ++--
.../1.1.2/Using-non-JVM-languages-with-Storm.html | 4 ++--
content/releases/1.1.2/Windowing.html | 4 ++--
content/releases/1.1.2/distcache-blobstore.html | 4 ++--
content/releases/1.1.2/dynamic-log-level-settings.html | 4 ++--
content/releases/1.1.2/dynamic-worker-profiling.html | 4 ++--
content/releases/1.1.2/flux.html | 4 ++--
content/releases/1.1.2/index.html | 4 ++--
content/releases/1.1.2/nimbus-ha-design.html | 4 ++--
content/releases/1.1.2/storm-cassandra.html | 4 ++--
content/releases/1.1.2/storm-elasticsearch.html | 4 ++--
content/releases/1.1.2/storm-eventhubs.html | 4 ++--
content/releases/1.1.2/storm-hbase.html | 4 ++--
content/releases/1.1.2/storm-hdfs.html | 4 ++--
content/releases/1.1.2/storm-hive.html | 4 ++--
content/releases/1.1.2/storm-jdbc.html | 4 ++--
content/releases/1.1.2/storm-jms-example.html | 4 ++--
content/releases/1.1.2/storm-jms-spring.html | 4 ++--
content/releases/1.1.2/storm-jms.html | 4 ++--
content/releases/1.1.2/storm-kafka-client.html | 4 ++--
content/releases/1.1.2/storm-kafka.html | 4 ++--
.../1.1.2/storm-metrics-profiling-internal-actions.html | 4 ++--
content/releases/1.1.2/storm-mongodb.html | 4 ++--
content/releases/1.1.2/storm-mqtt.html | 4 ++--
content/releases/1.1.2/storm-redis.html | 4 ++--
content/releases/1.1.2/storm-solr.html | 4 ++--
content/releases/1.1.2/storm-sql-example.html | 4 ++--
content/releases/1.1.2/storm-sql-internal.html | 4 ++--
content/releases/1.1.2/storm-sql-reference.html | 4 ++--
content/releases/1.1.2/storm-sql.html | 4 ++--
content/releases/1.1.2/windows-users-guide.html | 4 ++--
.../releases/1.2.1/Acking-framework-implementation.html | 4 ++--
content/releases/1.2.1/Classpath-handling.html | 4 ++--
content/releases/1.2.1/Clojure-DSL.html | 4 ++--
content/releases/1.2.1/Command-line-client.html | 4 ++--
content/releases/1.2.1/Common-patterns.html | 4 ++--
content/releases/1.2.1/Concepts.html | 4 ++--
content/releases/1.2.1/Configuration.html | 4 ++--
content/releases/1.2.1/Contributing-to-Storm.html | 4 ++--
.../releases/1.2.1/Creating-a-new-Storm-project.html | 4 ++--
content/releases/1.2.1/DSLs-and-multilang-adapters.html | 4 ++--
content/releases/1.2.1/Daemon-Fault-Tolerance.html | 4 ++--
.../Defining-a-non-jvm-language-dsl-for-storm.html | 4 ++--
content/releases/1.2.1/Distributed-RPC.html | 4 ++--
content/releases/1.2.1/Eventlogging.html | 4 ++--
content/releases/1.2.1/FAQ.html | 4 ++--
content/releases/1.2.1/Fault-tolerance.html | 4 ++--
.../releases/1.2.1/Guaranteeing-message-processing.html | 4 ++--
content/releases/1.2.1/Hooks.html | 4 ++--
content/releases/1.2.1/Implementation-docs.html | 4 ++--
.../releases/1.2.1/Installing-native-dependencies.html | 4 ++--
content/releases/1.2.1/Joins.html | 4 ++--
content/releases/1.2.1/Kestrel-and-Storm.html | 4 ++--
content/releases/1.2.1/Lifecycle-of-a-topology.html | 4 ++--
content/releases/1.2.1/Local-mode.html | 4 ++--
content/releases/1.2.1/Logs.html | 4 ++--
content/releases/1.2.1/Maven.html | 4 ++--
.../releases/1.2.1/Message-passing-implementation.html | 4 ++--
content/releases/1.2.1/Metrics.html | 4 ++--
content/releases/1.2.1/Multilang-protocol.html | 4 ++--
content/releases/1.2.1/Pacemaker.html | 4 ++--
content/releases/1.2.1/Powered-By.html | 4 ++--
content/releases/1.2.1/Project-ideas.html | 4 ++--
content/releases/1.2.1/Rationale.html | 4 ++--
.../1.2.1/Resource_Aware_Scheduler_overview.html | 4 ++--
.../Running-topologies-on-a-production-cluster.html | 4 ++--
content/releases/1.2.1/SECURITY.html | 4 ++--
content/releases/1.2.1/STORM-UI-REST-API.html | 4 ++--
.../releases/1.2.1/Serialization-(prior-to-0.6.0).html | 4 ++--
content/releases/1.2.1/Serialization.html | 4 ++--
content/releases/1.2.1/Serializers.html | 4 ++--
content/releases/1.2.1/Setting-up-a-Storm-cluster.html | 4 ++--
.../1.2.1/Setting-up-development-environment.html | 4 ++--
content/releases/1.2.1/Spout-implementations.html | 4 ++--
content/releases/1.2.1/State-checkpointing.html | 4 ++--
content/releases/1.2.1/Storm-Scheduler.html | 4 ++--
...ti-language-protocol-(versions-0.7.0-and-below).html | 4 ++--
content/releases/1.2.1/Structure-of-the-codebase.html | 4 ++--
.../releases/1.2.1/Support-for-non-java-languages.html | 4 ++--
content/releases/1.2.1/Transactional-topologies.html | 4 ++--
content/releases/1.2.1/Trident-API-Overview.html | 4 ++--
content/releases/1.2.1/Trident-RAS-API.html | 4 ++--
content/releases/1.2.1/Trident-spouts.html | 4 ++--
content/releases/1.2.1/Trident-state.html | 4 ++--
content/releases/1.2.1/Trident-tutorial.html | 4 ++--
content/releases/1.2.1/Troubleshooting.html | 4 ++--
content/releases/1.2.1/Tutorial.html | 4 ++--
...derstanding-the-parallelism-of-a-Storm-topology.html | 4 ++--
.../1.2.1/Using-non-JVM-languages-with-Storm.html | 4 ++--
content/releases/1.2.1/Windowing.html | 4 ++--
content/releases/1.2.1/distcache-blobstore.html | 4 ++--
content/releases/1.2.1/dynamic-log-level-settings.html | 4 ++--
content/releases/1.2.1/dynamic-worker-profiling.html | 4 ++--
content/releases/1.2.1/flux.html | 4 ++--
content/releases/1.2.1/index.html | 4 ++--
content/releases/1.2.1/metrics_v2.html | 4 ++--
content/releases/1.2.1/nimbus-ha-design.html | 4 ++--
content/releases/1.2.1/storm-cassandra.html | 4 ++--
content/releases/1.2.1/storm-elasticsearch.html | 4 ++--
content/releases/1.2.1/storm-eventhubs.html | 4 ++--
content/releases/1.2.1/storm-hbase.html | 4 ++--
content/releases/1.2.1/storm-hdfs.html | 4 ++--
content/releases/1.2.1/storm-hive.html | 4 ++--
content/releases/1.2.1/storm-jdbc.html | 4 ++--
content/releases/1.2.1/storm-jms-example.html | 4 ++--
content/releases/1.2.1/storm-jms-spring.html | 4 ++--
content/releases/1.2.1/storm-jms.html | 4 ++--
content/releases/1.2.1/storm-kafka-client.html | 4 ++--
content/releases/1.2.1/storm-kafka.html | 4 ++--
.../1.2.1/storm-metrics-profiling-internal-actions.html | 4 ++--
content/releases/1.2.1/storm-mongodb.html | 4 ++--
content/releases/1.2.1/storm-mqtt.html | 4 ++--
content/releases/1.2.1/storm-redis.html | 4 ++--
content/releases/1.2.1/storm-solr.html | 4 ++--
content/releases/1.2.1/storm-sql-example.html | 4 ++--
content/releases/1.2.1/storm-sql-internal.html | 4 ++--
content/releases/1.2.1/storm-sql-reference.html | 4 ++--
content/releases/1.2.1/storm-sql.html | 4 ++--
content/releases/1.2.1/windows-users-guide.html | 4 ++--
.../2.0.0-SNAPSHOT/Acking-framework-implementation.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Classpath-handling.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Clojure-DSL.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/Command-line-client.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Common-patterns.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Concepts.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Configuration.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/Contributing-to-Storm.html | 4 ++--
.../2.0.0-SNAPSHOT/Creating-a-new-Storm-project.html | 4 ++--
.../2.0.0-SNAPSHOT/DSLs-and-multilang-adapters.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/Daemon-Fault-Tolerance.html | 4 ++--
.../Defining-a-non-jvm-language-dsl-for-storm.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Distributed-RPC.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Eventlogging.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/FAQ.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Fault-tolerance.html | 4 ++--
.../2.0.0-SNAPSHOT/Guaranteeing-message-processing.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Hooks.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/IConfigLoader.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/Implementation-docs.html | 4 ++--
.../2.0.0-SNAPSHOT/Installing-native-dependencies.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Joins.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Kestrel-and-Storm.html | 4 ++--
.../2.0.0-SNAPSHOT/Lifecycle-of-a-topology.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Local-mode.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Logs.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Maven.html | 4 ++--
.../2.0.0-SNAPSHOT/Message-passing-implementation.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Metrics.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Multilang-protocol.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Pacemaker.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Performance.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Powered-By.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Project-ideas.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Rationale.html | 4 ++--
.../Resource_Aware_Scheduler_overview.html | 4 ++--
.../Running-topologies-on-a-production-cluster.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/SECURITY.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/STORM-UI-REST-API.html | 4 ++--
.../2.0.0-SNAPSHOT/Serialization-(prior-to-0.6.0).html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Serialization.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Serializers.html | 4 ++--
.../2.0.0-SNAPSHOT/Setting-up-a-Storm-cluster.html | 4 ++--
.../Setting-up-development-environment.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/Spout-implementations.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/State-checkpointing.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Storm-Scheduler.html | 4 ++--
...ti-language-protocol-(versions-0.7.0-and-below).html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Stream-API.html | 4 ++--
.../2.0.0-SNAPSHOT/Structure-of-the-codebase.html | 4 ++--
.../2.0.0-SNAPSHOT/Support-for-non-java-languages.html | 4 ++--
.../2.0.0-SNAPSHOT/Transactional-topologies.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/Trident-API-Overview.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Trident-RAS-API.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Trident-spouts.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Trident-state.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Trident-tutorial.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Troubleshooting.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Tutorial.html | 4 ++--
...derstanding-the-parallelism-of-a-Storm-topology.html | 4 ++--
.../Using-non-JVM-languages-with-Storm.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/Windowing.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/cgroups_in_storm.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/distcache-blobstore.html | 4 ++--
.../2.0.0-SNAPSHOT/dynamic-log-level-settings.html | 4 ++--
.../2.0.0-SNAPSHOT/dynamic-worker-profiling.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/flux.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/index.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/metrics_v2.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/nimbus-ha-design.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-cassandra.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/storm-elasticsearch.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-eventhubs.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-hbase.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-hdfs.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-hive.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-jdbc.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-jms-example.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-jms-spring.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-jms.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-kafka-client.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-kafka.html | 4 ++--
.../storm-metrics-profiling-internal-actions.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-metricstore.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-mongodb.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-mqtt.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-redis.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-solr.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-sql-example.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-sql-internal.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/storm-sql-reference.html | 4 ++--
content/releases/2.0.0-SNAPSHOT/storm-sql.html | 4 ++--
.../releases/2.0.0-SNAPSHOT/windows-users-guide.html | 4 ++--
.../current/Acking-framework-implementation.html | 4 ++--
content/releases/current/Classpath-handling.html | 4 ++--
content/releases/current/Clojure-DSL.html | 4 ++--
content/releases/current/Command-line-client.html | 4 ++--
content/releases/current/Common-patterns.html | 4 ++--
content/releases/current/Concepts.html | 4 ++--
content/releases/current/Configuration.html | 4 ++--
content/releases/current/Contributing-to-Storm.html | 4 ++--
.../releases/current/Creating-a-new-Storm-project.html | 4 ++--
.../releases/current/DSLs-and-multilang-adapters.html | 4 ++--
content/releases/current/Daemon-Fault-Tolerance.html | 4 ++--
.../Defining-a-non-jvm-language-dsl-for-storm.html | 4 ++--
content/releases/current/Distributed-RPC.html | 4 ++--
content/releases/current/Eventlogging.html | 4 ++--
content/releases/current/FAQ.html | 4 ++--
content/releases/current/Fault-tolerance.html | 4 ++--
.../current/Guaranteeing-message-processing.html | 4 ++--
content/releases/current/Hooks.html | 4 ++--
content/releases/current/Implementation-docs.html | 4 ++--
.../current/Installing-native-dependencies.html | 4 ++--
content/releases/current/Joins.html | 4 ++--
content/releases/current/Kestrel-and-Storm.html | 4 ++--
content/releases/current/Lifecycle-of-a-topology.html | 4 ++--
content/releases/current/Local-mode.html | 4 ++--
content/releases/current/Logs.html | 4 ++--
content/releases/current/Maven.html | 4 ++--
.../current/Message-passing-implementation.html | 4 ++--
content/releases/current/Metrics.html | 4 ++--
content/releases/current/Multilang-protocol.html | 4 ++--
content/releases/current/Pacemaker.html | 4 ++--
content/releases/current/Powered-By.html | 4 ++--
content/releases/current/Project-ideas.html | 4 ++--
content/releases/current/Rationale.html | 4 ++--
.../current/Resource_Aware_Scheduler_overview.html | 4 ++--
.../Running-topologies-on-a-production-cluster.html | 4 ++--
content/releases/current/SECURITY.html | 4 ++--
content/releases/current/STORM-UI-REST-API.html | 4 ++--
.../current/Serialization-(prior-to-0.6.0).html | 4 ++--
content/releases/current/Serialization.html | 4 ++--
content/releases/current/Serializers.html | 4 ++--
.../releases/current/Setting-up-a-Storm-cluster.html | 4 ++--
.../current/Setting-up-development-environment.html | 4 ++--
content/releases/current/Spout-implementations.html | 4 ++--
content/releases/current/State-checkpointing.html | 4 ++--
content/releases/current/Storm-Scheduler.html | 4 ++--
...ti-language-protocol-(versions-0.7.0-and-below).html | 4 ++--
content/releases/current/Structure-of-the-codebase.html | 4 ++--
.../current/Support-for-non-java-languages.html | 4 ++--
content/releases/current/Transactional-topologies.html | 4 ++--
content/releases/current/Trident-API-Overview.html | 4 ++--
content/releases/current/Trident-RAS-API.html | 4 ++--
content/releases/current/Trident-spouts.html | 4 ++--
content/releases/current/Trident-state.html | 4 ++--
content/releases/current/Trident-tutorial.html | 4 ++--
content/releases/current/Troubleshooting.html | 4 ++--
content/releases/current/Tutorial.html | 4 ++--
...derstanding-the-parallelism-of-a-Storm-topology.html | 4 ++--
.../current/Using-non-JVM-languages-with-Storm.html | 4 ++--
content/releases/current/Windowing.html | 4 ++--
content/releases/current/distcache-blobstore.html | 4 ++--
.../releases/current/dynamic-log-level-settings.html | 4 ++--
content/releases/current/dynamic-worker-profiling.html | 4 ++--
content/releases/current/flux.html | 4 ++--
content/releases/current/index.html | 4 ++--
content/releases/current/metrics_v2.html | 4 ++--
content/releases/current/nimbus-ha-design.html | 4 ++--
content/releases/current/storm-cassandra.html | 4 ++--
content/releases/current/storm-elasticsearch.html | 4 ++--
content/releases/current/storm-eventhubs.html | 4 ++--
content/releases/current/storm-hbase.html | 4 ++--
content/releases/current/storm-hdfs.html | 4 ++--
content/releases/current/storm-hive.html | 4 ++--
content/releases/current/storm-jdbc.html | 4 ++--
content/releases/current/storm-jms-example.html | 4 ++--
content/releases/current/storm-jms-spring.html | 4 ++--
content/releases/current/storm-jms.html | 4 ++--
content/releases/current/storm-kafka-client.html | 4 ++--
content/releases/current/storm-kafka.html | 4 ++--
.../storm-metrics-profiling-internal-actions.html | 4 ++--
content/releases/current/storm-mongodb.html | 4 ++--
content/releases/current/storm-mqtt.html | 4 ++--
content/releases/current/storm-redis.html | 4 ++--
content/releases/current/storm-solr.html | 4 ++--
content/releases/current/storm-sql-example.html | 4 ++--
content/releases/current/storm-sql-internal.html | 4 ++--
content/releases/current/storm-sql-reference.html | 4 ++--
content/releases/current/storm-sql.html | 4 ++--
content/releases/current/windows-users-guide.html | 4 ++--
content/talksAndVideos.html | 4 ++--
446 files changed, 902 insertions(+), 890 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/Powered-By.html
----------------------------------------------------------------------
diff --git a/content/Powered-By.html b/content/Powered-By.html
index cf2df24..c8709a6 100644
--- a/content/Powered-By.html
+++ b/content/Powered-By.html
@@ -142,7 +142,7 @@
<p class="post-meta"></p>
-<p>Want to be added to this page? Send an email <a href="mailto:dev@storm.apache.org">here</a>.</p>
+<div class="documentation-content"><p>Want to be added to this page? Send an email <a href="mailto:dev@storm.apache.org">here</a>.</p>
<table class="table table-striped">
@@ -1177,7 +1177,7 @@ We are using Storm to track internet threats from varied sources around the web.
</table>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/contribute/BYLAWS.html
----------------------------------------------------------------------
diff --git a/content/contribute/BYLAWS.html b/content/contribute/BYLAWS.html
index 242e290..2a0b584 100644
--- a/content/contribute/BYLAWS.html
+++ b/content/contribute/BYLAWS.html
@@ -142,7 +142,7 @@
<p class="post-meta"></p>
-<h2 id="roles-and-responsibilities">Roles and Responsibilities</h2>
+<div class="documentation-content"><h2 id="roles-and-responsibilities">Roles and Responsibilities</h2>
<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>
@@ -356,7 +356,7 @@
<td><a href="mailto:dev@storm.apache.org">dev@storm.apache.org</a></td>
</tr>
</tbody></table>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/contribute/Contributing-to-Storm.html
----------------------------------------------------------------------
diff --git a/content/contribute/Contributing-to-Storm.html b/content/contribute/Contributing-to-Storm.html
index ff4c290..da28f96 100644
--- a/content/contribute/Contributing-to-Storm.html
+++ b/content/contribute/Contributing-to-Storm.html
@@ -142,7 +142,7 @@
<p class="post-meta"></p>
-<h3 id="getting-started-with-contributing">Getting started with contributing</h3>
+<div class="documentation-content"><h3 id="getting-started-with-contributing">Getting started with contributing</h3>
<p>Some of the issues on the <a href="https://issues.apache.org/jira/browse/STORM">issue tracker</a> are marked with the "Newbie" label. If you're interesting in contributing to Storm but don't know where to begin, these are good issues to start with. These issues are a great way to get your feet wet with learning the codebase because they require learning about only an isolated portion of the codebase and are a relatively small amount of work.</p>
@@ -167,7 +167,7 @@
<h3 id="contributing-documentation">Contributing documentation</h3>
<p>Documentation contributions are very welcome! The best way to send contributions is as emails through the mailing list.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/contribute/People.html
----------------------------------------------------------------------
diff --git a/content/contribute/People.html b/content/contribute/People.html
index cddc6e3..c52cc58 100644
--- a/content/contribute/People.html
+++ b/content/contribute/People.html
@@ -142,7 +142,7 @@
<p class="post-meta"></p>
-<h2 id="project-management">Project Management</h2>
+<div class="documentation-content"><h2 id="project-management">Project Management</h2>
<table class="table table-striped table-bordered table-responsive">
<thead>
@@ -434,7 +434,7 @@
</tr>
</table>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/css/style.css
----------------------------------------------------------------------
diff --git a/content/css/style.css b/content/css/style.css
index 0302cb7..57ea25c 100644
--- a/content/css/style.css
+++ b/content/css/style.css
@@ -532,7 +532,19 @@ footer hr {
border-top: none;
}
+.documentation-content table tr {
+ background-color: #fff;
+ border-top: 1px solid #c6cbd1;
+}
+.documentation-content table th, .documentation-content table td {
+ padding: 6px 13px;
+ border: 1px solid #dfe2e5;
+}
+
+.documentation-content table tr:nth-child(2n) {
+ background-color: #f6f8fa;
+}
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/feed.xml
----------------------------------------------------------------------
diff --git a/content/feed.xml b/content/feed.xml
index 19d5acd..9fdda0e 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -5,8 +5,8 @@
<description></description>
<link>http://storm.apache.org/</link>
<atom:link href="http://storm.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Sat, 12 May 2018 17:59:26 +0200</pubDate>
- <lastBuildDate>Sat, 12 May 2018 17:59:26 +0200</lastBuildDate>
+ <pubDate>Tue, 15 May 2018 17:16:07 +0200</pubDate>
+ <lastBuildDate>Tue, 15 May 2018 17:16:07 +0200</lastBuildDate>
<generator>Jekyll v3.6.2</generator>
<item>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/news.html
----------------------------------------------------------------------
diff --git a/content/news.html b/content/news.html
index 15765f1..a45df5f 100644
--- a/content/news.html
+++ b/content/news.html
@@ -142,7 +142,7 @@
<p class="post-meta"></p>
-<div class="row">
+<div class="documentation-content"><div class="row">
<div class="col-md-3">
<ul class="news" id="news-list">
@@ -234,7 +234,7 @@
</div>
</div>
-</div>
+</div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Acking-framework-implementation.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Acking-framework-implementation.html b/content/releases/1.0.6/Acking-framework-implementation.html
index b57c18b..59c87d8 100644
--- a/content/releases/1.0.6/Acking-framework-implementation.html
+++ b/content/releases/1.0.6/Acking-framework-implementation.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p><a href="https://github.com/apache/incubator-storm/blob/46c3ba7/storm-core/src/clj/backtype/storm/daemon/acker.clj#L28">Storm's acker</a> tracks completion of each tupletree with a checksum hash: each time a tuple is sent, its value is XORed into the checksum, and each time a tuple is acked its value is XORed in again. If all tuples have been successfully acked, the checksum will be zero (the odds that the checksum will be zero otherwise are vanishingly small).</p>
+<div class="documentation-content"><p><a href="https://github.com/apache/incubator-storm/blob/46c3ba7/storm-core/src/clj/backtype/storm/daemon/acker.clj#L28">Storm's acker</a> tracks completion of each tupletree with a checksum hash: each time a tuple is sent, its value is XORed into the checksum, and each time a tuple is acked its value is XORed in again. If all tuples have been successfully acked, the checksum will be zero (the odds that the checksum will be zero otherwise are vanishingly small).</p>
<p>You can read a bit more about the <a href="Guaranteeing-message-processing.html#what-is-storms-reliability-api">reliability mechanism</a> elsewhere on the wiki -- this explains the internal details.</p>
@@ -180,7 +180,7 @@
<p>Internally, it holds several HashMaps ('buckets') of its own, each holding a cohort of records that will expire at the same time. Let's call the longest-lived bucket death row, and the most recent the nursery. Whenever a value is <code>.put()</code> to the RotatingMap, it is relocated to the nursery -- and removed from any other bucket it might have been in (effectively resetting its death clock).</p>
<p>Whenever its owner calls <code>.rotate()</code>, the RotatingMap advances each cohort one step further towards expiration. (Typically, Storm objects call rotate on every receipt of a system tick stream tuple.) If there are any key-value pairs in the former death row bucket, the RotatingMap invokes a callback (given in the constructor) for each key-value pair, letting its owner take appropriate action (eg, failing a tuple.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Clojure-DSL.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Clojure-DSL.html b/content/releases/1.0.6/Clojure-DSL.html
index e917f7c..75368b6 100644
--- a/content/releases/1.0.6/Clojure-DSL.html
+++ b/content/releases/1.0.6/Clojure-DSL.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm comes with a Clojure DSL for defining spouts, bolts, and topologies. The Clojure DSL has access to everything the Java API exposes, so if you're a Clojure user you can code Storm topologies without touching Java at all. The Clojure DSL is defined in the source in the <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/clojure.clj">org.apache.storm.clojure</a> namespace.</p>
+<div class="documentation-content"><p>Storm comes with a Clojure DSL for defining spouts, bolts, and topologies. The Clojure DSL has access to everything the Java API exposes, so if you're a Clojure user you can code Storm topologies without touching Java at all. The Clojure DSL is defined in the source in the <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/clojure.clj">org.apache.storm.clojure</a> namespace.</p>
<p>This page outlines all the pieces of the Clojure DSL, including:</p>
@@ -371,7 +371,7 @@
<h3 id="testing-topologies">Testing topologies</h3>
<p><a href="http://www.pixelmachine.org/2011/12/17/Testing-Storm-Topologies.html">This blog post</a> and its <a href="http://www.pixelmachine.org/2011/12/21/Testing-Storm-Topologies-Part-2.html">follow-up</a> give a good overview of Storm's powerful built-in facilities for testing topologies in Clojure.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Command-line-client.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Command-line-client.html b/content/releases/1.0.6/Command-line-client.html
index 20ca10c..16bd00f 100644
--- a/content/releases/1.0.6/Command-line-client.html
+++ b/content/releases/1.0.6/Command-line-client.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page describes all the commands that are possible with the "storm" command line client. To learn how to set up your "storm" client to talk to a remote cluster, follow the instructions in <a href="Setting-up-development-environment.html">Setting up development environment</a>.</p>
+<div class="documentation-content"><p>This page describes all the commands that are possible with the "storm" command line client. To learn how to set up your "storm" client to talk to a remote cluster, follow the instructions in <a href="Setting-up-development-environment.html">Setting up development environment</a>.</p>
<p>These commands are:</p>
@@ -411,7 +411,7 @@ and timeout is integer seconds.</p>
<p>Syntax: <code>storm help [command]</code></p>
<p>Print one help message or list of available commands</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Common-patterns.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Common-patterns.html b/content/releases/1.0.6/Common-patterns.html
index ed5e979..20aea41 100644
--- a/content/releases/1.0.6/Common-patterns.html
+++ b/content/releases/1.0.6/Common-patterns.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page lists a variety of common patterns in Storm topologies.</p>
+<div class="documentation-content"><p>This page lists a variety of common patterns in Storm topologies.</p>
<ol>
<li>Streaming joins</li>
@@ -225,7 +225,7 @@
<p><code>KeyedFairBolt</code> also wraps the bolt containing your logic and makes sure your topology processes multiple DRPC invocations at the same time, instead of doing them serially one at a time.</p>
<p>See <a href="Distributed-RPC.html">Distributed RPC</a> for more details.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Concepts.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Concepts.html b/content/releases/1.0.6/Concepts.html
index 14aae54..7969af2 100644
--- a/content/releases/1.0.6/Concepts.html
+++ b/content/releases/1.0.6/Concepts.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page lists the main concepts of Storm and links to resources where you can find more information. The concepts discussed are:</p>
+<div class="documentation-content"><p>This page lists the main concepts of Storm and links to resources where you can find more information. The concepts discussed are:</p>
<ol>
<li>Topologies</li>
@@ -268,7 +268,7 @@
<ul>
<li><a href="javadocs/org/apache/storm/Config.html#TOPOLOGY_WORKERS">Config.TOPOLOGY_WORKERS</a>: this config sets the number of workers to allocate for executing the topology</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Configuration.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Configuration.html b/content/releases/1.0.6/Configuration.html
index 42cb905..8044370 100644
--- a/content/releases/1.0.6/Configuration.html
+++ b/content/releases/1.0.6/Configuration.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm has a variety of configurations for tweaking the behavior of nimbus, supervisors, and running topologies. Some configurations are system configurations and cannot be modified on a topology by topology basis, whereas other configurations can be modified per topology. </p>
+<div class="documentation-content"><p>Storm has a variety of configurations for tweaking the behavior of nimbus, supervisors, and running topologies. Some configurations are system configurations and cannot be modified on a topology by topology basis, whereas other configurations can be modified per topology. </p>
<p>Every configuration has a default value defined in <a href="http://github.com/apache/storm/blob/v1.0.6/conf/defaults.yaml">defaults.yaml</a> in the Storm codebase. You can override these configurations by defining a storm.yaml in the classpath of Nimbus and the supervisors. Finally, you can define a topology-specific configuration that you submit along with your topology when using <a href="javadocs/org/apache/storm/StormSubmitter.html">StormSubmitter</a>. However, the topology-specific configuration can only override configs prefixed with "TOPOLOGY".</p>
@@ -175,7 +175,7 @@
<li><a href="Running-topologies-on-a-production-cluster.html">Running topologies on a production cluster</a>: lists useful configurations when running topologies on a cluster</li>
<li><a href="Local-mode.html">Local mode</a>: lists useful configurations when using local mode</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Contributing-to-Storm.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Contributing-to-Storm.html b/content/releases/1.0.6/Contributing-to-Storm.html
index af3b3bc..887c574 100644
--- a/content/releases/1.0.6/Contributing-to-Storm.html
+++ b/content/releases/1.0.6/Contributing-to-Storm.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h3 id="getting-started-with-contributing">Getting started with contributing</h3>
+<div class="documentation-content"><h3 id="getting-started-with-contributing">Getting started with contributing</h3>
<p>Some of the issues on the <a href="https://issues.apache.org/jira/browse/STORM">issue tracker</a> are marked with the <a href="https://issues.apache.org/jira/browse/STORM-2891?jql=project%20%3D%20STORM%20AND%20status%20%3D%20Open%20AND%20labels%20in%20(newbie%2C%20%22newbie%2B%2B%22)">"Newbie"</a> label. If you're interested in contributing to Storm but don't know where to begin, these are good issues to start with. These issues are a great way to get your feet wet with learning the codebase because they require learning about only an isolated portion of the codebase and are a relatively small amount of work.</p>
@@ -172,7 +172,7 @@
<h3 id="contributing-documentation">Contributing documentation</h3>
<p>Documentation contributions are very welcome! The best way to send contributions is as emails through the mailing list.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Creating-a-new-Storm-project.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Creating-a-new-Storm-project.html b/content/releases/1.0.6/Creating-a-new-Storm-project.html
index f919cfa..251e502 100644
--- a/content/releases/1.0.6/Creating-a-new-Storm-project.html
+++ b/content/releases/1.0.6/Creating-a-new-Storm-project.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page outlines how to set up a Storm project for development. The steps are:</p>
+<div class="documentation-content"><p>This page outlines how to set up a Storm project for development. The steps are:</p>
<ol>
<li>Add Storm jars to classpath</li>
@@ -166,7 +166,7 @@
<p>For more information on writing topologies in other languages, see <a href="Using-non-JVM-languages-with-Storm.html">Using non-JVM languages with Storm</a>.</p>
<p>To test that everything is working in Eclipse, you should now be able to <code>Run</code> the <code>WordCountTopology.java</code> file. You will see messages being emitted at the console for 10 seconds.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/DSLs-and-multilang-adapters.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/DSLs-and-multilang-adapters.html b/content/releases/1.0.6/DSLs-and-multilang-adapters.html
index d05295d..107b114 100644
--- a/content/releases/1.0.6/DSLs-and-multilang-adapters.html
+++ b/content/releases/1.0.6/DSLs-and-multilang-adapters.html
@@ -144,14 +144,14 @@
<p class="post-meta"></p>
-<ul>
+<div class="documentation-content"><ul>
<li><a href="https://github.com/velvia/ScalaStorm">Scala DSL</a></li>
<li><a href="https://github.com/colinsurprenant/redstorm">JRuby DSL</a></li>
<li><a href="Clojure-DSL.html">Clojure DSL</a></li>
<li><a href="https://github.com/tomdz/storm-esper">Storm/Esper integration</a>: Streaming SQL on top of Storm</li>
<li><a href="https://github.com/dan-blanchard/io-storm">io-storm</a>: Perl multilang adapter</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Daemon-Fault-Tolerance.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Daemon-Fault-Tolerance.html b/content/releases/1.0.6/Daemon-Fault-Tolerance.html
index 2aac7ee..c5c36af 100644
--- a/content/releases/1.0.6/Daemon-Fault-Tolerance.html
+++ b/content/releases/1.0.6/Daemon-Fault-Tolerance.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm has several different daemon processes. Nimbus that schedules workers, supervisors that launch and kill workers, the log viewer that gives access to logs, and the UI that shows the status of a cluster.</p>
+<div class="documentation-content"><p>Storm has several different daemon processes. Nimbus that schedules workers, supervisors that launch and kill workers, the log viewer that gives access to logs, and the UI that shows the status of a cluster.</p>
<h2 id="what-happens-when-a-worker-dies">What happens when a worker dies?</h2>
@@ -169,7 +169,7 @@
<h2 id="how-does-storm-guarantee-data-processing">How does Storm guarantee data processing?</h2>
<p>Storm provides mechanisms to guarantee data processing even if nodes die or messages are lost. See <a href="Guaranteeing-message-processing.html">Guaranteeing message processing</a> for the details.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Defining-a-non-jvm-language-dsl-for-storm.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Defining-a-non-jvm-language-dsl-for-storm.html b/content/releases/1.0.6/Defining-a-non-jvm-language-dsl-for-storm.html
index b8dfa1a..713d544 100644
--- a/content/releases/1.0.6/Defining-a-non-jvm-language-dsl-for-storm.html
+++ b/content/releases/1.0.6/Defining-a-non-jvm-language-dsl-for-storm.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>The right place to start to learn how to make a non-JVM DSL for Storm is <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/storm.thrift">storm-core/src/storm.thrift</a>. Since Storm topologies are just Thrift structures, and Nimbus is a Thrift daemon, you can create and submit topologies in any language.</p>
+<div class="documentation-content"><p>The right place to start to learn how to make a non-JVM DSL for Storm is <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/storm.thrift">storm-core/src/storm.thrift</a>. Since Storm topologies are just Thrift structures, and Nimbus is a Thrift daemon, you can create and submit topologies in any language.</p>
<p>When you create the Thrift structs for spouts and bolts, the code for the spout or bolt is specified in the ComponentObject struct:</p>
<div class="highlight"><pre><code class="language-" data-lang="">union ComponentObject {
@@ -165,7 +165,7 @@
<div class="highlight"><pre><code class="language-java" data-lang="java"><span class="kt">void</span> <span class="nf">submitTopology</span><span class="o">(</span><span class="mi">1</span><span class="o">:</span> <span class="n">string</span> <span class="n">name</span><span class="o">,</span> <span class="mi">2</span><span class="o">:</span> <span class="n">string</span> <span class="n">uploadedJarLocation</span><span class="o">,</span> <span class="mi">3</span><span class="o">:</span> <span class="n">string</span> <span class="n">jsonConf</span><span class="o">,</span> <span class="mi">4</span><span class="o">:</span> <span class="n">StormTopology</span> <span class="n">topology</span><span class="o">)</span> <span class="kd">throws</span> <span class="o">(</span><span class="mi">1</span><span class="o">:</span> <span class="n">AlreadyAliveException</span> <span class="n">e</span><span class="o">,</span> <span class="mi">2</span><span class="o">:</span> <span class="n">InvalidTop
ologyException</span> <span class="n">ite</span><span class="o">);</span>
</code></pre></div>
<p>Finally, one of the key things to do in a non-JVM DSL is make it easy to define the entire topology in one file (the bolts, spouts, and the definition of the topology).</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Distributed-RPC.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Distributed-RPC.html b/content/releases/1.0.6/Distributed-RPC.html
index f11dc24..f699d63 100644
--- a/content/releases/1.0.6/Distributed-RPC.html
+++ b/content/releases/1.0.6/Distributed-RPC.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>The idea behind distributed RPC (DRPC) is to parallelize the computation of really intense functions on the fly using Storm. The Storm topology takes in as input a stream of function arguments, and it emits an output stream of the results for each of those function calls. </p>
+<div class="documentation-content"><p>The idea behind distributed RPC (DRPC) is to parallelize the computation of really intense functions on the fly using Storm. The Storm topology takes in as input a stream of function arguments, and it emits an output stream of the results for each of those function calls. </p>
<p>DRPC is not so much a feature of Storm as it is a pattern expressed from Storm's primitives of streams, spouts, bolts, and topologies. DRPC could have been packaged as a separate library from Storm, but it's so useful that it's bundled with Storm.</p>
@@ -330,7 +330,7 @@
<li>KeyedFairBolt for weaving the processing of multiple requests at the same time</li>
<li>How to use <code>CoordinatedBolt</code> directly</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Eventlogging.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Eventlogging.html b/content/releases/1.0.6/Eventlogging.html
index dcd75e8..78eca14 100644
--- a/content/releases/1.0.6/Eventlogging.html
+++ b/content/releases/1.0.6/Eventlogging.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h1 id="introduction">Introduction</h1>
+<div class="documentation-content"><h1 id="introduction">Introduction</h1>
<p>Topology event inspector provides the ability to view the tuples as it flows through different stages in a storm topology.
This could be useful for inspecting the tuples emitted at a spout or a bolt in the topology pipeline while the topology is running, without stopping or redeploying the topology. The normal flow of tuples from the spouts to the bolts is not affected by turning on event logging.</p>
@@ -247,7 +247,7 @@ clicking "Debug" under component actions.</p>
*/</span>
<span class="kt">void</span> <span class="nf">close</span><span class="o">();</span>
<span class="o">}</span>
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/FAQ.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/FAQ.html b/content/releases/1.0.6/FAQ.html
index 49e1a4d..73a0066 100644
--- a/content/releases/1.0.6/FAQ.html
+++ b/content/releases/1.0.6/FAQ.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h2 id="best-practices">Best Practices</h2>
+<div class="documentation-content"><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>
@@ -276,7 +276,7 @@
<li>When possible, make your process incremental: each value that comes in makes the answer more an more true. A Trident ReducerAggregator is an operator that takes a prior result and a set of new records and returns a new result. This lets the result be cached and serialized to a datastore; if a server drops off line for a day and then comes back with a full day's worth of data in a rush, the old results will be calmly retrieved and updated.</li>
<li>Lambda architecture: Record all events into an archival store (S3, HBase, HDFS) on receipt. in the fast layer, once the time window is clear, process the bucket to get an actionable answer, and ignore everything older than the time window. Periodically run a global aggregation to calculate a "correct" answer.</li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Fault-tolerance.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Fault-tolerance.html b/content/releases/1.0.6/Fault-tolerance.html
index 20551f4..0cdc4e3 100644
--- a/content/releases/1.0.6/Fault-tolerance.html
+++ b/content/releases/1.0.6/Fault-tolerance.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page explains the design details of Storm that make it a fault-tolerant system.</p>
+<div class="documentation-content"><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>
@@ -169,7 +169,7 @@
<h2 id="how-does-storm-guarantee-data-processing">How does Storm guarantee data processing?</h2>
<p>Storm provides mechanisms to guarantee data processing even if nodes die or messages are lost. See <a href="Guaranteeing-message-processing.html">Guaranteeing message processing</a> for the details.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Guaranteeing-message-processing.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Guaranteeing-message-processing.html b/content/releases/1.0.6/Guaranteeing-message-processing.html
index 0fc48a7..29c9423 100644
--- a/content/releases/1.0.6/Guaranteeing-message-processing.html
+++ b/content/releases/1.0.6/Guaranteeing-message-processing.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm offers several different levels of guaranteed message processing, including best effort, at least once, and exactly once through <a href="Trident-tutorial.html">Trident</a>.
+<div class="documentation-content"><p>Storm offers several different levels of guaranteed message processing, including 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-fully-processed">What does it mean for a message to be "fully processed"?</h3>
@@ -301,7 +301,7 @@ This page describes how Storm can guarantee at least once processing.</p>
<p>The second way is to remove reliability on a message by message basis. You can turn off tracking for an individual spout tuple by omitting a message id in the <code>SpoutOutputCollector.emit</code> method.</p>
<p>Finally, if you don't care if a particular subset of the tuples downstream in the topology fail to be processed, you can emit them as unanchored tuples. Since they're not anchored to any spout tuples, they won't cause any spout tuples to fail if they aren't acked.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Hooks.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Hooks.html b/content/releases/1.0.6/Hooks.html
index 4707651..567923a 100644
--- a/content/releases/1.0.6/Hooks.html
+++ b/content/releases/1.0.6/Hooks.html
@@ -144,13 +144,13 @@
<p class="post-meta"></p>
-<p>Storm provides hooks with which you can insert custom code to run on any number of events within Storm. You create a hook by extending the <a href="javadocs/org/apache/storm/hooks/BaseTaskHook.html">BaseTaskHook</a> class and overriding the appropriate method for the event you want to catch. There are two ways to register your hook:</p>
+<div class="documentation-content"><p>Storm provides hooks with which you can insert custom code to run on any number of events within Storm. You create a hook by extending the <a href="javadocs/org/apache/storm/hooks/BaseTaskHook.html">BaseTaskHook</a> class and overriding the appropriate method for the event you want to catch. There are two ways to register your hook:</p>
<ol>
<li>In the open method of your spout or prepare method of your bolt using the <a href="javadocs/org/apache/storm/task/TopologyContext.html#addTaskHook">TopologyContext</a> method.</li>
<li>Through the Storm configuration using the <a href="javadocs/org/apache/storm/Config.html#TOPOLOGY_AUTO_TASK_HOOKS">"topology.auto.task.hooks"</a> config. These hooks are automatically registered in every spout or bolt, and are useful for doing things like integrating with a custom monitoring system.</li>
</ol>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Implementation-docs.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Implementation-docs.html b/content/releases/1.0.6/Implementation-docs.html
index 3811c0c..fed0756 100644
--- a/content/releases/1.0.6/Implementation-docs.html
+++ b/content/releases/1.0.6/Implementation-docs.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This section of the wiki is dedicated to explaining how Storm is implemented. You should have a good grasp of how to use Storm before reading these sections. </p>
+<div class="documentation-content"><p>This section of the wiki is dedicated to explaining how Storm is implemented. You should have a good grasp of how to use Storm before reading these sections. </p>
<ul>
<li><a href="Structure-of-the-codebase.html">Structure of the codebase</a></li>
@@ -154,7 +154,7 @@
<li><a href="nimbus-ha-design.html">Nimbus HA</a></li>
<li><a href="storm-sql-internal.html">Storm SQL</a></li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Installing-native-dependencies.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Installing-native-dependencies.html b/content/releases/1.0.6/Installing-native-dependencies.html
index 89fdf74..5d7fff7 100644
--- a/content/releases/1.0.6/Installing-native-dependencies.html
+++ b/content/releases/1.0.6/Installing-native-dependencies.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>The native dependencies are only needed on actual Storm clusters. When running Storm in local mode, Storm uses a pure Java messaging system so that you don't need to install native dependencies on your development machine.</p>
+<div class="documentation-content"><p>The native dependencies are only needed on actual Storm clusters. When running Storm in local mode, Storm uses a pure Java messaging system so that you don't need to install native dependencies on your development machine.</p>
<p>Installing ZeroMQ and JZMQ is usually straightforward. Sometimes, however, people run into issues with autoconf and get strange errors. If you run into any issues, please email the <a href="http://groups.google.com/group/storm-user">Storm mailing list</a> or come get help in the #storm-user room on freenode. </p>
@@ -175,7 +175,7 @@ sudo make install
</ol>
<p>If you run into any errors when running <code>./configure</code>, <a href="http://stackoverflow.com/questions/3522248/how-do-i-compile-jzmq-for-zeromq-on-osx">this thread</a> may provide a solution.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Kestrel-and-Storm.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Kestrel-and-Storm.html b/content/releases/1.0.6/Kestrel-and-Storm.html
index 0ef1966..dacc415 100644
--- a/content/releases/1.0.6/Kestrel-and-Storm.html
+++ b/content/releases/1.0.6/Kestrel-and-Storm.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page explains how to use Storm to consume items from a Kestrel cluster.</p>
+<div class="documentation-content"><p>This page explains how to use Storm to consume items from a Kestrel cluster.</p>
<h2 id="preliminaries">Preliminaries</h2>
@@ -334,7 +334,7 @@ Than, wait about 5 seconds in order to avoid a ConnectException.
Now execute the program to add items to the queue and launch the Storm topology. The order in which you launch the programs is of no importance.
If you run the topology with TOPOLOGY_DEBUG you should see tuples being emitted in the topology.
-</code></pre></div>
+</code></pre></div></div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Lifecycle-of-a-topology.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Lifecycle-of-a-topology.html b/content/releases/1.0.6/Lifecycle-of-a-topology.html
index 2999f9f..85fcd42 100644
--- a/content/releases/1.0.6/Lifecycle-of-a-topology.html
+++ b/content/releases/1.0.6/Lifecycle-of-a-topology.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>(<strong>NOTE</strong>: this page is based on the 0.7.1 code; many things have changed since then, including a split between tasks and executors, and a reorganization of the code under <code>storm-core/src</code> rather than <code>src/</code>.)</p>
+<div class="documentation-content"><p>(<strong>NOTE</strong>: this page is based on the 0.7.1 code; many things have changed since then, including a split between tasks and executors, and a reorganization of the code under <code>storm-core/src</code> rather than <code>src/</code>.)</p>
<p>This page explains in detail the lifecycle of a topology from running the "storm jar" command to uploading the topology to Nimbus to the supervisors starting/stopping workers to workers and tasks setting themselves up. It also explains how Nimbus monitors topologies and how topologies are shutdown when they are killed.</p>
@@ -261,7 +261,7 @@
<li>Removing a topology cleans out the assignment and static information from ZK <a href="https://github.com/apache/storm/blob/0.7.1/src/clj/org/apache/storm/daemon/nimbus.clj#L116">code</a></li>
<li>A separate cleanup thread runs the <code>do-cleanup</code> function which will clean up the heartbeat dir and the jars/configs stored locally. <a href="https://github.com/apache/storm/blob/0.7.1/src/clj/org/apache/storm/daemon/nimbus.clj#L577">code</a></li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Local-mode.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Local-mode.html b/content/releases/1.0.6/Local-mode.html
index 11db27e..e2a1839 100644
--- a/content/releases/1.0.6/Local-mode.html
+++ b/content/releases/1.0.6/Local-mode.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Local mode simulates a Storm cluster in process and is useful for developing and testing topologies. Running topologies in local mode is similar to running topologies <a href="Running-topologies-on-a-production-cluster.html">on a cluster</a>. </p>
+<div class="documentation-content"><p>Local mode simulates a Storm cluster in process and is useful for developing and testing topologies. Running topologies in local mode is similar to running topologies <a href="Running-topologies-on-a-production-cluster.html">on a cluster</a>. </p>
<p>To create an in-process cluster, simply use the <code>LocalCluster</code> class. For example:</p>
<div class="highlight"><pre><code class="language-java" data-lang="java"><span class="kn">import</span> <span class="nn">org.apache.storm.LocalCluster</span><span class="o">;</span>
@@ -164,7 +164,7 @@
<li><strong>Config.TOPOLOGY_MAX_TASK_PARALLELISM</strong>: This config puts a ceiling on the number of threads spawned for a single component. Oftentimes production topologies have a lot of parallelism (hundreds of threads) which places unreasonable load when trying to test the topology in local mode. This config lets you easy control that parallelism.</li>
<li><strong>Config.TOPOLOGY_DEBUG</strong>: When this is set to true, Storm will log a message every time a tuple is emitted from any spout or bolt. This is extremely useful for debugging.</li>
</ol>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Logs.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Logs.html b/content/releases/1.0.6/Logs.html
index f9a7637..266141a 100644
--- a/content/releases/1.0.6/Logs.html
+++ b/content/releases/1.0.6/Logs.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Logs in Storm are essential for tracking the status, operations, error messages and debug information for all the
+<div class="documentation-content"><p>Logs in Storm are essential for tracking the status, operations, error messages and debug information for all the
daemons (e.g., nimbus, supervisor, logviewer, drpc, ui, pacemaker) and topologies' workers.</p>
<h3 id="location-of-the-logs">Location of the Logs</h3>
@@ -171,7 +171,7 @@ Log Search supports searching in a certain log file or in all of a topology'
<p>Search in a topology: a user can also search a string for a certain topology by clicking the icon of magnifying lens at the top right corner of the UI page. This means the UI will try to search on all the supervisor nodes in a distributed way to find the matched string in all logs for this topology. The search can happen for either normal text log files or rolled zip log files by checking/unchecking the "Search archived logs:" box. Then the matched results can be shown on the UI with url links, directing the user to the certain logs on each supervisor node. This powerful feature is very helpful for users to find certain problematic supervisor nodes running this topology.</p>
<p><img src="images/search-a-topology.png" alt="Search in a topology" title="Search in a topology"></p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Maven.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Maven.html b/content/releases/1.0.6/Maven.html
index 810d427..39ea13e 100644
--- a/content/releases/1.0.6/Maven.html
+++ b/content/releases/1.0.6/Maven.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>To develop topologies, you'll need the Storm jars on your classpath. You should either include the unpacked jars in the classpath for your project or use Maven to include Storm as a development dependency. Storm is hosted on Maven Central. To include Storm in your project as a development dependency, add the following to your pom.xml:</p>
+<div class="documentation-content"><p>To develop topologies, you'll need the Storm jars on your classpath. You should either include the unpacked jars in the classpath for your project or use Maven to include Storm as a development dependency. Storm is hosted on Maven Central. To include Storm in your project as a development dependency, add the following to your pom.xml:</p>
<div class="highlight"><pre><code class="language-xml" data-lang="xml"><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.storm<span class="nt"></groupId></span>
<span class="nt"><artifactId></span>storm-core<span class="nt"></artifactId></span>
@@ -157,7 +157,7 @@
<h3 id="developing-storm">Developing Storm</h3>
<p>Please refer to <a href="http://github.com/apache/storm/blob/v1.0.6/DEVELOPER.md">DEVELOPER.md</a> for more details.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Message-passing-implementation.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Message-passing-implementation.html b/content/releases/1.0.6/Message-passing-implementation.html
index 8170a39..9f33ef0 100644
--- a/content/releases/1.0.6/Message-passing-implementation.html
+++ b/content/releases/1.0.6/Message-passing-implementation.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>(Note: this walkthrough is out of date as of 0.8.0. 0.8.0 revamped the message passing infrastructure to be based on the Disruptor)</p>
+<div class="documentation-content"><p>(Note: this walkthrough is out of date as of 0.8.0. 0.8.0 revamped the message passing infrastructure to be based on the Disruptor)</p>
<p>This page walks through how emitting and transferring tuples works in Storm.</p>
@@ -186,7 +186,7 @@
</ul></li>
</ul></li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Metrics.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Metrics.html b/content/releases/1.0.6/Metrics.html
index d90c0fd..2ff22c6 100644
--- a/content/releases/1.0.6/Metrics.html
+++ b/content/releases/1.0.6/Metrics.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Storm exposes a metrics interface to report summary statistics across the full topology.
+<div class="documentation-content"><p>Storm exposes a metrics interface to report summary statistics across the full topology.
It's used internally to track the numbers you see in the Nimbus UI console: counts of executes and acks; average process latency per bolt; worker heap usage; and so forth.</p>
<h3 id="metric-types">Metric Types</h3>
@@ -255,7 +255,7 @@ It's used internally to track the numbers you see in the Nimbus UI console:
<p>The <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/daemon/builtin_metrics.clj">builtin metrics</a> instrument Storm itself.</p>
<p><a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/daemon/builtin_metrics.clj">builtin_metrics.clj</a> sets up data structures for the built-in metrics, and facade methods that the other framework components can use to update them. The metrics themselves are calculated in the calling code -- see for example <a href="http://github.com/apache/storm/blob/v1.0.6/storm-core/src/clj/org/apache/storm/daemon/executor.clj#358"><code>ack-spout-msg</code></a> in <code>clj/b/s/daemon/daemon/executor.clj</code></p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Multilang-protocol.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Multilang-protocol.html b/content/releases/1.0.6/Multilang-protocol.html
index 8bfa617..b430d39 100644
--- a/content/releases/1.0.6/Multilang-protocol.html
+++ b/content/releases/1.0.6/Multilang-protocol.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>This page explains the multilang protocol as of Storm 0.7.1. Versions prior to 0.7.1 used a somewhat different protocol, documented [here](Storm-multi-language-protocol-(versions-0.7.0-and-below).html).</p>
+<div class="documentation-content"><p>This page explains the multilang protocol as of Storm 0.7.1. Versions prior to 0.7.1 used a somewhat different protocol, documented [here](Storm-multi-language-protocol-(versions-0.7.0-and-below).html).</p>
<h1 id="storm-multi-language-protocol">Storm Multi-Language Protocol</h1>
@@ -404,7 +404,7 @@ subprocess periodically. Heartbeat tuple looks like:</p>
</code></pre></div>
<p>When subprocess receives heartbeat tuple, it must send a <code>sync</code> command back to
ShellBolt.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Pacemaker.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Pacemaker.html b/content/releases/1.0.6/Pacemaker.html
index fa2d6fa..8d18f28 100644
--- a/content/releases/1.0.6/Pacemaker.html
+++ b/content/releases/1.0.6/Pacemaker.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h3 id="introduction">Introduction</h3>
+<div class="documentation-content"><h3 id="introduction">Introduction</h3>
<p>Pacemaker is a storm daemon designed to process heartbeats from workers. As Storm is scaled up, ZooKeeper begins to become a bottleneck due to high volumes of writes from workers doing heartbeats. Lots of writes to disk and too much traffic across the network is generated as ZooKeeper tries to maintain consistency.</p>
@@ -253,7 +253,7 @@ On a 270 supervisor cluster, fully scheduled with topologies, Pacemaker resource
<p>There is an easy route to HA for Pacemaker. Unlike ZooKeeper, Pacemaker should be able to scale horizontally without overhead. By contrast, with ZooKeeper, there are diminishing returns when adding ZK nodes.</p>
<p>In short, a single Pacemaker node should be able to handle many times the load that a ZooKeeper cluster can, and future HA work allowing horizontal scaling will increase that even farther.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Powered-By.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Powered-By.html b/content/releases/1.0.6/Powered-By.html
index 229c5a7..06c4e04 100644
--- a/content/releases/1.0.6/Powered-By.html
+++ b/content/releases/1.0.6/Powered-By.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Want to be added to this page? Send an email <a href="mailto:nathan.marz@gmail.com">here</a>.</p>
+<div class="documentation-content"><p>Want to be added to this page? Send an email <a href="mailto:nathan.marz@gmail.com">here</a>.</p>
<table>
@@ -1169,7 +1169,7 @@ We are using Storm to track internet threats from varied sources around the web.
</table>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Project-ideas.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Project-ideas.html b/content/releases/1.0.6/Project-ideas.html
index abdec39..05e6b93 100644
--- a/content/releases/1.0.6/Project-ideas.html
+++ b/content/releases/1.0.6/Project-ideas.html
@@ -144,12 +144,12 @@
<p class="post-meta"></p>
-<ul>
+<div class="documentation-content"><ul>
<li><strong>DSLs for non-JVM languages:</strong> These DSL's should be all-inclusive and not require any Java for the creation of topologies, spouts, or bolts. Since topologies are <a href="http://thrift.apache.org/">Thrift</a> structs, Nimbus is a Thrift service, and bolts can be written in any language, this is possible.</li>
<li><strong>Online machine learning algorithms:</strong> Something like <a href="http://mahout.apache.org/">Mahout</a> but for online algorithms</li>
<li><strong>Suite of performance benchmarks:</strong> These benchmarks should test Storm's performance on CPU and IO intensive workloads. There should be benchmarks for different classes of applications, such as stream processing (where throughput is the priority) and distributed RPC (where latency is the priority). </li>
</ul>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Rationale.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Rationale.html b/content/releases/1.0.6/Rationale.html
index d21caf8..5c1ad13 100644
--- a/content/releases/1.0.6/Rationale.html
+++ b/content/releases/1.0.6/Rationale.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. There's no hack that will turn Hadoop into a realtime system; realtime data processing has a fundamentally different set of requirements than batch processing.</p>
+<div class="documentation-content"><p>The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. There's no hack that will turn Hadoop into a realtime system; realtime data processing has a fundamentally different set of requirements than batch processing.</p>
<p>However, realtime data processing at massive scale is becoming more and more of a requirement for businesses. The lack of a "Hadoop of realtime" has become the biggest hole in the data processing ecosystem.</p>
@@ -176,7 +176,7 @@
<li><strong>Fault-tolerant</strong>: If there are faults during execution of your computation, Storm will reassign tasks as necessary. Storm makes sure that a computation can run forever (or until you kill the computation).</li>
<li><strong>Programming language agnostic</strong>: Robust and scalable realtime processing shouldn't be limited to a single platform. Storm topologies and processing components can be defined in any language, making Storm accessible to nearly anyone.</li>
</ol>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Resource_Aware_Scheduler_overview.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Resource_Aware_Scheduler_overview.html b/content/releases/1.0.6/Resource_Aware_Scheduler_overview.html
index d06a9e3..2f51750 100644
--- a/content/releases/1.0.6/Resource_Aware_Scheduler_overview.html
+++ b/content/releases/1.0.6/Resource_Aware_Scheduler_overview.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h1 id="introduction">Introduction</h1>
+<div class="documentation-content"><h1 id="introduction">Introduction</h1>
<p>The purpose of this document is to provide a description of the Resource Aware Scheduler for the Storm distributed real-time computation system. This document will provide you with both a high level description of the resource aware scheduler in Storm</p>
@@ -364,7 +364,7 @@ DEV => 20 – 29
<p>We should never evict a topology from a user that does not have his or her resource guarantees satisfied. The following flow chart should describe the logic for the eviction process.</p>
<p><img src="images/resource_aware_scheduler_default_eviction_strategy.svg" alt="Viewing metrics with VisualVM"></p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/Running-topologies-on-a-production-cluster.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/Running-topologies-on-a-production-cluster.html b/content/releases/1.0.6/Running-topologies-on-a-production-cluster.html
index 084780c..e107a08 100644
--- a/content/releases/1.0.6/Running-topologies-on-a-production-cluster.html
+++ b/content/releases/1.0.6/Running-topologies-on-a-production-cluster.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<p>Running topologies on a production cluster is similar to running in <a href="Local-mode.html">Local mode</a>. Here are the steps:</p>
+<div class="documentation-content"><p>Running topologies on a production cluster is similar to running in <a href="Local-mode.html">Local mode</a>. Here are the steps:</p>
<p>1) Define the topology (Use <a href="javadocs/org/apache/storm/topology/TopologyBuilder.html">TopologyBuilder</a> if defining using Java)</p>
@@ -212,7 +212,7 @@
<p>The best place to monitor a topology is using the Storm UI. The Storm UI provides information about errors happening in tasks and fine-grained stats on the throughput and latency performance of each component of each running topology.</p>
<p>You can also look at the worker logs on the cluster machines.</p>
-
+</div>
</div>
http://git-wip-us.apache.org/repos/asf/storm-site/blob/df5612be/content/releases/1.0.6/SECURITY.html
----------------------------------------------------------------------
diff --git a/content/releases/1.0.6/SECURITY.html b/content/releases/1.0.6/SECURITY.html
index 0b9f5de..c2dcd5f 100644
--- a/content/releases/1.0.6/SECURITY.html
+++ b/content/releases/1.0.6/SECURITY.html
@@ -144,7 +144,7 @@
<p class="post-meta"></p>
-<h1 id="running-apache-storm-securely">Running Apache Storm Securely</h1>
+<div class="documentation-content"><h1 id="running-apache-storm-securely">Running Apache Storm Securely</h1>
<p>Apache Storm offers a range of configuration options when trying to secure
your cluster. By default all authentication and authorization is disabled but
@@ -680,7 +680,7 @@ on all possible worker hosts.</p>
| storm.zookeeper.topology.auth.payload | A string representing the payload for topology Zookeeper authentication. |</p>
<p>Note: If storm.zookeeper.topology.auth.payload isn't set,storm will generate a ZooKeeper secret payload for MD5-digest with generateZookeeperDigestSecretPayload() method.</p>
-
+</div>
</div>