Skip to content

Files

Latest commit

ca69fc8 · Aug 30, 2015

History

History
This branch is 1 commit ahead of, 31045 commits behind apache/spark:master.

docs

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Jun 18, 2015
Jul 2, 2015
Jul 2, 2015
Apr 9, 2015
Jul 2, 2015
Aug 5, 2015
Jun 3, 2015
Jun 27, 2015
Feb 5, 2015
Aug 4, 2015
Apr 9, 2015
Aug 27, 2015
Sep 8, 2013
Mar 19, 2015
Aug 19, 2015
Jun 11, 2015
May 14, 2015
Sep 11, 2013
Jun 9, 2015
May 30, 2014
Apr 28, 2015
Aug 21, 2015
Aug 24, 2015
Aug 24, 2015
Aug 28, 2015
Aug 30, 2015
Aug 28, 2015
May 23, 2015
Aug 26, 2015
Jul 1, 2015
Aug 27, 2015
Mar 3, 2015
May 10, 2015
Aug 19, 2015
Jul 31, 2015
Jul 31, 2015
Aug 19, 2015
Aug 30, 2015
Aug 18, 2015
Aug 18, 2015
Aug 28, 2015
Jul 1, 2015
Mar 17, 2015
May 18, 2015
Aug 18, 2015
Aug 3, 2015
Aug 22, 2015
May 30, 2014
Jul 31, 2015
Aug 12, 2015
Aug 19, 2015
May 30, 2014
May 1, 2015
Aug 3, 2015
Aug 12, 2015
Aug 29, 2015
Sep 8, 2014
Jun 14, 2015
Jul 1, 2015
Aug 27, 2015
Aug 28, 2015
Aug 23, 2015
May 11, 2015
Aug 7, 2015

Welcome to the Spark documentation!

This readme will walk you through navigating and building the Spark documentation, which is included here with the Spark source code. You can also find documentation specific to release versions of Spark at http://spark.apache.org/documentation.html.

Read on to learn more about viewing documentation in plain text (i.e., markdown) or building the documentation yourself. Why build it yourself? So that you have the docs that corresponds to whichever version of Spark you currently have checked out of revision control.

Prerequisites

The Spark documentation build uses a number of tools to build HTML docs and API docs in Scala, Python and R. To get started you can run the following commands

$ sudo gem install jekyll
$ sudo gem install jekyll-redirect-from
$ sudo pip install Pygments
$ sudo pip install sphinx
$ Rscript -e 'install.packages(c("knitr", "devtools"), repos="http://cran.stat.ucla.edu/")'

Generating the Documentation HTML

We include the Spark documentation as part of the source (as opposed to using a hosted wiki, such as the github wiki, as the definitive documentation) to enable the documentation to evolve along with the source code and be captured by revision control (currently git). This way the code automatically includes the version of the documentation that is relevant regardless of which version or release you have checked out or downloaded.

In this directory you will find textfiles formatted using Markdown, with an ".md" suffix. You can read those text files directly if you want. Start with index.md.

Execute jekyll build from the docs/ directory to compile the site. Compiling the site with Jekyll will create a directory called _site containing index.html as well as the rest of the compiled files.

$ cd docs
$ jekyll build

You can modify the default Jekyll build as follows:

# Skip generating API docs (which takes a while)
$ SKIP_API=1 jekyll build
# Serve content locally on port 4000
$ jekyll serve --watch
# Build the site with extra features used on the live page
$ PRODUCTION=1 jekyll build

API Docs (Scaladoc, Sphinx, roxygen2)

You can build just the Spark scaladoc by running build/sbt unidoc from the SPARK_PROJECT_ROOT directory.

Similarly, you can build just the PySpark docs by running make html from the SPARK_PROJECT_ROOT/python/docs directory. Documentation is only generated for classes that are listed as public in __init__.py. The SparkR docs can be built by running SPARK_PROJECT_ROOT/R/create-docs.sh.

When you run jekyll in the docs directory, it will also copy over the scaladoc for the various Spark subprojects into the docs directory (and then also into the _site directory). We use a jekyll plugin to run build/sbt unidoc before building the site so if you haven't run it (recently) it may take some time as it generates all of the scaladoc. The jekyll plugin also generates the PySpark docs Sphinx.

NOTE: To skip the step of building and copying over the Scala, Python, R API docs, run SKIP_API=1 jekyll.