Apache Spark - A unified analytics engine for large-scale data processing
Go to file
Chen Chao 5d98cfc1c8 maintain arbitrary state data for each key
RT

Author: Chen Chao <crazyjvm@gmail.com>

Closes #114 from CrazyJvm/patch-1 and squashes the following commits:

dcb0df5 [Chen Chao] maintain arbitrary state data for each key
2014-03-09 22:42:12 -07:00
assembly SPARK-1184: Update the distribution tar.gz to include spark-assembly jar 2014-03-05 16:52:58 -08:00
bagel SPARK-1193. Fix indentation in pom.xmls 2014-03-07 23:10:35 -08:00
bin SPARK-929: Fully deprecate usage of SPARK_MEM 2014-03-09 11:08:39 -07:00
conf Revert "[SPARK-1150] fix repo location in create script" 2014-03-01 17:15:38 -08:00
core SPARK-782 Clean up for ASM dependency. 2014-03-09 13:17:07 -07:00
data moved user scripts to bin folder 2013-09-23 12:46:48 +08:00
dev [java8API] SPARK-964 Investigate the potential for using JDK 8 lambda expressions for the Java/Scala APIs 2014-03-03 22:31:30 -08:00
docker SPARK-1136: Fix FaultToleranceTest for Docker 0.8.1 2014-03-07 10:22:27 -08:00
docs maintain arbitrary state data for each key 2014-03-09 22:42:12 -07:00
ec2 SPARK-1156: allow user to login into a cluster without slaves 2014-03-05 21:47:34 -08:00
examples SPARK-1193. Fix indentation in pom.xmls 2014-03-07 23:10:35 -08:00
external SPARK-1193. Fix indentation in pom.xmls 2014-03-07 23:10:35 -08:00
extras [java8API] SPARK-964 Investigate the potential for using JDK 8 lambda expressions for the Java/Scala APIs 2014-03-03 22:31:30 -08:00
graphx SPARK-782 Clean up for ASM dependency. 2014-03-09 13:17:07 -07:00
mllib SPARK-1193. Fix indentation in pom.xmls 2014-03-07 23:10:35 -08:00
project SPARK-782 Clean up for ASM dependency. 2014-03-09 13:17:07 -07:00
python SPARK-929: Fully deprecate usage of SPARK_MEM 2014-03-09 11:08:39 -07:00
repl SPARK-782 Clean up for ASM dependency. 2014-03-09 13:17:07 -07:00
sbin [SPARK-1041] remove dead code in start script, remind user to set that in spark-env.sh 2014-02-22 20:21:15 -08:00
sbt Allow sbt to use more than 1G of heap. 2014-03-07 23:23:59 -08:00
streaming SPARK-1193. Fix indentation in pom.xmls 2014-03-07 23:10:35 -08:00
tools SPARK-1193. Fix indentation in pom.xmls 2014-03-07 23:10:35 -08:00
yarn SPARK-1193. Fix indentation in pom.xmls 2014-03-07 23:10:35 -08:00
.gitignore Restricting /lib to top level directory in .gitignore 2014-01-20 20:39:30 -08:00
LICENSE Merge the old sbt-launch-lib.bash with the new sbt-launcher jar downloading logic. 2014-03-02 00:35:23 -08:00
make-distribution.sh fix make-distribution.sh show version: command not found 2014-01-09 00:34:53 +08:00
NOTICE Add Apache license headers and LICENSE and NOTICE files 2013-07-16 17:21:33 -07:00
pom.xml SPARK-782 Clean up for ASM dependency. 2014-03-09 13:17:07 -07:00
README.md Removed reference to incubation in README.md. 2014-02-26 16:52:26 -08:00
scalastyle-config.xml Merge pull request #567 from ScrapCodes/style2. 2014-02-09 22:17:52 -08:00

Apache Spark

Lightning-Fast Cluster Computing - http://spark.apache.org/

Online Documentation

You can find the latest Spark documentation, including a programming guide, on the project webpage at http://spark.apache.org/documentation.html. This README file only contains basic setup instructions.

Building

Spark requires Scala 2.10. The project is built using Simple Build Tool (SBT), which can be obtained here. If SBT is installed we will use the system version of sbt otherwise we will attempt to download it automatically. To build Spark and its example programs, run:

./sbt/sbt assembly

Once you've built Spark, the easiest way to start using it is the shell:

./bin/spark-shell

Or, for the Python API, the Python shell (./bin/pyspark).

Spark also comes with several sample programs in the examples directory. To run one of them, use ./bin/run-example <class> <params>. For example:

./bin/run-example org.apache.spark.examples.SparkLR local[2]

will run the Logistic Regression example locally on 2 CPUs.

Each of the example programs prints usage help if no params are given.

All of the Spark samples take a <master> parameter that is the cluster URL to connect to. This can be a mesos:// or spark:// URL, or "local" to run locally with one thread, or "local[N]" to run locally with N threads.

Running tests

Testing first requires Building Spark. Once Spark is built, tests can be run using:

./sbt/sbt test

A Note About Hadoop Versions

Spark uses the Hadoop core library to talk to HDFS and other Hadoop-supported storage systems. Because the protocols have changed in different versions of Hadoop, you must build Spark against the same version that your cluster runs. You can change the version by setting the SPARK_HADOOP_VERSION environment when building Spark.

For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and other Hadoop versions without YARN, use:

# Apache Hadoop 1.2.1
$ SPARK_HADOOP_VERSION=1.2.1 sbt/sbt assembly

# Cloudera CDH 4.2.0 with MapReduce v1
$ SPARK_HADOOP_VERSION=2.0.0-mr1-cdh4.2.0 sbt/sbt assembly

For Apache Hadoop 2.2.X, 2.1.X, 2.0.X, 0.23.x, Cloudera CDH MRv2, and other Hadoop versions with YARN, also set SPARK_YARN=true:

# Apache Hadoop 2.0.5-alpha
$ SPARK_HADOOP_VERSION=2.0.5-alpha SPARK_YARN=true sbt/sbt assembly

# Cloudera CDH 4.2.0 with MapReduce v2
$ SPARK_HADOOP_VERSION=2.0.0-cdh4.2.0 SPARK_YARN=true sbt/sbt assembly

# Apache Hadoop 2.2.X and newer
$ SPARK_HADOOP_VERSION=2.2.0 SPARK_YARN=true sbt/sbt assembly

When developing a Spark application, specify the Hadoop version by adding the "hadoop-client" artifact to your project's dependencies. For example, if you're using Hadoop 1.2.1 and build your application using SBT, add this entry to libraryDependencies:

"org.apache.hadoop" % "hadoop-client" % "1.2.1"

If your project is built with Maven, add this to your POM file's <dependencies> section:

<dependency>
  <groupId>org.apache.hadoop</groupId>
  <artifactId>hadoop-client</artifactId>
  <version>1.2.1</version>
</dependency>

Configuration

Please refer to the Configuration guide in the online documentation for an overview on how to configure Spark.

Contributing to Spark

Contributions via GitHub pull requests are gladly accepted from their original author. Along with any pull requests, please state that the contribution is your original work and that you license the work to the project under the project's open source license. Whether or not you state this explicitly, by submitting any copyrighted material via pull request, email, or other means you agree to license the material under the project's open source license and warrant that you have the legal authority to do so.