THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
The Apache Spark team welcomes all types of contributions, whether they be bug reports, providing help to new users, documentation, or new code patches.
| Table of Contents |
|---|
Reporting, Answer, and Triaging Issues
The Spark community has two platforms for discussing user issues and requirements:
- The spark-user mailing list is the place to go for usage questions.
- The Apache Spark JIRA is the project's issue tracker, for reporting reproducible bugs or posting feature requests.
A great way to contribute to Spark is to help answer user questions on the mailing list. There are always many new Spark users; taking a few minutes to help answer a question is a very valuable community service! On the JIRA issue tracker, helping investigate, isolate, and reproduce bugs reported on the issue tracker is a great way to get more familiar with Spark components, and a good first step towards contributing code to those componentsIf 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
We prefer to receive contributions in the form of GitHub pull requests. Start by opening an issue for your change on the Spark Project JIRA (and make sure to search whether there's an existing issue). For code reviews, we use the github.com/apache/spark repository.
...