Reporting Issues
If you'd like to report a bug in Spark or ask for a new feature, open an issue on the Apache Spark JIRA. For general usage help, you should email the user mailing list.
Contributing Code
The Apache Spark team welcomes contributions in the form of GitHub pull requests. Please send pull requests against the github.com/apache/incubator-spark repository. If you've previously forked Spark from its old location, you will need to fork incubator-spark
instead.
Here are a few tips to get your contribution in:
- Break your work into small, single-purpose patches if possible. It’s much harder to merge in a large change with a lot of disjoint features.
- Submit the patch as a GitHub pull request. For a tutorial, see the GitHub guides on forking a repo and sending a pull request.
- Follow the style of the existing codebase. Specifically, we use standard Scala style guide, but with the following changes:
- Maximum line length of 100 characters.
- Always import packages using absolute paths (e.g.
scala.collection.Map
instead ofcollection.Map
). - No "infix" syntax for methods other than operators. For example, don’t write
table containsKey myKey
; replace it withtable.containsKey(myKey)
.
- Make sure that your code passes the unit tests. You can run the tests with
sbt/sbt assembly
and thensbt/sbt test
in the root directory of Spark. It's important to runassembly
first as some of the tests depend on compiled JARs. - Add new unit tests for your code. We use ScalaTest for testing. Just add a new Suite in
core/src/test
, or methods to an existing Suite.
If you’d like to report a bug but don’t have time to fix it, you can still post it to our issue tracker, or email the mailing list.