tree: bf52c5efae1d865a083bc72b8038793c8a87229f [path history] [tgz]
  1. Acking-framework-implementation.md
  2. Classpath-handling.md
  3. Clojure-DSL.md
  4. ClusterMetrics.md
  5. Command-line-client.md
  6. Common-patterns.md
  7. Concepts.md
  8. Configuration.md
  9. Contributing-to-Storm.md
  10. Creating-a-new-Storm-project.md
  11. DSLs-and-multilang-adapters.md
  12. Daemon-Fault-Tolerance.md
  13. Defining-a-non-jvm-language-dsl-for-storm.md
  14. Distributed-RPC.md
  15. Eventlogging.md
  16. FAQ.md
  17. Fault-tolerance.md
  18. Guaranteeing-message-processing.md
  19. Hooks.md
  20. IConfigLoader.md
  21. Implementation-docs.md
  22. Installing-native-dependencies.md
  23. Joins.md
  24. Kestrel-and-Storm.md
  25. Lifecycle-of-a-topology.md
  26. Local-mode.md
  27. Logs.md
  28. Maven.md
  29. Message-passing-implementation.md
  30. Metrics.md
  31. Multilang-protocol.md
  32. Pacemaker.md
  33. Performance.md
  34. Project-ideas.md
  35. README.md
  36. Rationale.md
  37. Resource_Aware_Scheduler_overview.md
  38. Running-topologies-on-a-production-cluster.md
  39. SECURITY.md
  40. STORM-UI-REST-API.md
  41. Serialization-(prior-to-0.6.0).md
  42. Serialization.md
  43. Serializers.md
  44. Setting-up-a-Storm-cluster.md
  45. Setting-up-a-Storm-project-in-Eclipse.md
  46. Setting-up-development-environment.md
  47. Spout-implementations.md
  48. State-checkpointing.md
  49. Storm-Scheduler.md
  50. Storm-multi-language-protocol-(versions-0.7.0-and-below).md
  51. Stream-API.md
  52. Structure-of-the-codebase.md
  53. Support-for-non-java-languages.md
  54. Transactional-topologies.md
  55. Trident-API-Overview.md
  56. Trident-RAS-API.md
  57. Trident-spouts.md
  58. Trident-state.md
  59. Trident-tutorial.md
  60. Troubleshooting.md
  61. Tutorial.md
  62. Understanding-the-parallelism-of-a-Storm-topology.md
  63. Using-non-JVM-languages-with-Storm.md
  64. Windowing.md
  65. cgroups_in_storm.md
  66. distcache-blobstore.md
  67. dynamic-log-level-settings.md
  68. dynamic-worker-profiling.md
  69. favicon.ico
  70. flux.md
  71. images/
  72. index.md
  73. metrics_v2.md
  74. nimbus-ha-design.md
  75. storm-cassandra.md
  76. storm-elasticsearch.md
  77. storm-eventhubs.md
  78. storm-hbase.md
  79. storm-hdfs.md
  80. storm-hive.md
  81. storm-jdbc.md
  82. storm-jms-example.md
  83. storm-jms-spring.md
  84. storm-jms.md
  85. storm-kafka-client.md
  86. storm-kinesis.md
  87. storm-metricstore.md
  88. storm-mongodb.md
  89. storm-mqtt.md
  90. storm-opentsdb.md
  91. storm-pmml.md
  92. storm-redis.md
  93. storm-rocketmq.md
  94. storm-solr.md
  95. storm-sql-example.md
  96. storm-sql-internal.md
  97. storm-sql-reference.md
  98. storm-sql.md
  99. windows-users-guide.md
docs/README.md

Apache Storm Website and Documentation

This is the source for the Release specific part of the Apache Storm website and documentation. It is statically generated using jekyll.

Generate Javadoc

You have to generate javadoc on project root before generating document site.

mvn javadoc:javadoc -Dnotimestamp=true
mvn javadoc:aggregate -DreportOutputDirectory=./docs/ -DdestDir=javadocs -Dnotimestamp=true

You need to create distribution package with gpg certificate. Please refer here.

Site Generation

First install jekyll (assuming you have ruby installed):

gem install jekyll

Generate the site, and start a server locally:

cd docs
jekyll serve -w

The -w option tells jekyll to watch for changes to files and regenerate the site automatically when any content changes.

Point your browser to http://localhost:4000

By default, jekyll will generate the site in a _site directory.

This will only show the portion of the documentation that is specific to this release.

Adding a new release to the website

In order to add a new relase, you must have committer access to Storm's subversion repository at https://svn.apache.org/repos/asf/storm/site.

Release documentation is placed under the releases directory named after the release version. Most metadata about the release will be generated automatically from the name using a jekyll plugin. Or by plaing them in the _data/releases.yml file.

To create a new release run the following from the main git directory

mvn javadoc:javadoc -Dnotimestamp=true
mvn javadoc:aggregate -DreportOutputDirectory=./docs/ -DdestDir=javadocs -Dnotimestamp=true
mkdir ${path_to_svn}/releases/${release_name}
#Copy everything over, and compare checksums, except for things that are part of the site,
# and are not release specific like the _* directories that are jekyll specific
# assests/ css/ and README.md
rsync -ac --delete --exclude _\* --exclude assets --exclude css --exclude README.md ./docs/ ${path_to_svn}/releases/${release_name}
cd ${path_to_svn}
svn add releases/${release_name}
svn commit

to publish a new release run

cd ${path_to_svn}
jekyll build -d publish/
svn add publish/ #Add any new files
svn commit

How release specific docs work

Release specific documentation is controlled by a jekyll plugin releases.rb

If the plugin is running from the git repo the config storm_release_only is set and teh plugin will treat all of the markdown files as release sepcific file.

If it is running from the subversion repositiory it will look in the releases driectory for release sepcific docs.

http://svn.apache.org/viewvc/storm/site/releases/

Each sub directory named after the release in question. The “current” release is pointed to by a symlink in that directory called current.

The plugin sets three configs for each release page.

  • version - the version number of the release/directory
  • git-tree-base - a link to a directory in github that this version is on
  • git-blob-base - a link to to where on github that this version is on, but should be used when pointing to files.

If storm_release_only is set for the project the version is determined from the maven pom.xml and the branch is the current branch in git. If it is not set the version is determined by the name of the sub-directory and branch is assumed to be a "v#{version}" which corresponds with our naming conventions. For SNAPSHOT releases you will need to override this in _data/releases.yml

The plugin also augments the site.data.releases dataset. Each release in the list includes the following, and each can be set in _data/releases.yml to override what is automatically generated by the plugin.

  • git-tag-or-branch - tag or branch name on github/apache/storm
  • git-tree-base - a link to a directory in github that this version is on
  • git-blob-base - a link to to where on github that this version is on, but should be used when pointing to files.
  • base-name - name of the release files to download, without the .tar.gz
  • has-download - if this is an official release and a download link should be created.

So if you wanted to create a link to a file on github inside the release specific docs you would create a link like

[LICENSE]([DEVELOPER.md]({{page.git-blob-base}}/LICENSE)

If you wanted to create a maven string to tell people what dependency to use you would do something like

<dependency>
  ...
  <version>{{version}}</version>
</dependency>

If you want to refer to a javadoc for the current release use a relative path. It will be in the javadocs subdirectory.

[TopologyBuilder](javadocs/org/apache/storm/topology/TopologyBuilder.html)