spark git commit: [SPARK-4012] stop SparkContext when the exception is thrown from an infinite loop

Repository: spark Updated Branches: refs/heads/master 645cf3fcc - 2c3f83c34 [SPARK-4012] stop SparkContext when the exception is thrown from an infinite loop https://issues.apache.org/jira/browse/SPARK-4012 This patch is a resubmission for https://github.com/apache/spark/pull/2864 What I

spark git commit: [SPARK-6222][Streaming] Dont delete checkpoint data when doing pre-batch-start checkpoint

Repository: spark Updated Branches: refs/heads/master 540b2a4ea - 645cf3fcc [SPARK-6222][Streaming] Dont delete checkpoint data when doing pre-batch-start checkpoint This is another alternative approach to https://github.com/apache/spark/pull/4964/ I think this is a simpler fix that can be

spark git commit: [SPARK-6222][Streaming] Dont delete checkpoint data when doing pre-batch-start checkpoint

Repository: spark Updated Branches: refs/heads/branch-1.3 1723f0591 - 03e263f5b [SPARK-6222][Streaming] Dont delete checkpoint data when doing pre-batch-start checkpoint This is another alternative approach to https://github.com/apache/spark/pull/4964/ I think this is a simpler fix that can

spark git commit: [SPARK-5843] [API] Allowing map-side combine to be specified in Java.

Repository: spark Updated Branches: refs/heads/master 797f8a000 - 3c4e486b9 [SPARK-5843] [API] Allowing map-side combine to be specified in Java. Specifically, when calling JavaPairRDD.combineByKey(), there is a new six-parameter method that exposes the map-side-combine boolean as the fifth

spark git commit: [SPARK-6402][DOC] - Remove some refererences to shark in docs and ec2

Repository: spark Updated Branches: refs/heads/master 2c3f83c34 - 797f8a000 [SPARK-6402][DOC] - Remove some refererences to shark in docs and ec2 EC2 script and job scheduling documentation still refered to Shark. I removed these references. I also removed a remaining `SHARK_VERSION`

spark git commit: Tighten up field/method visibility in Executor and made some code more clear to read.

Repository: spark Updated Branches: refs/heads/master f17d43b03 - 0745a305f Tighten up field/method visibility in Executor and made some code more clear to read. I was reading Executor just now and found that some latest changes introduced some weird code path with too much monadic chaining

spark git commit: [SPARK-6219] [Build] Check that Python code compiles

Repository: spark Updated Branches: refs/heads/master 3b5aaa6a5 - f17d43b03 [SPARK-6219] [Build] Check that Python code compiles This PR expands the Python lint checks so that they check for obvious compilation errors in our Python code. For example: ``` $ ./dev/lint-python Python lint

spark git commit: [SPARK-6291] [MLLIB] GLM toString toDebugString

Repository: spark Updated Branches: refs/heads/master 3c4e486b9 - dda4dedca [SPARK-6291] [MLLIB] GLM toString toDebugString GLM toString prints out intercept, numFeatures. For LogisticRegression and SVM model, toString also prints out numClasses, threshold. GLM toDebugString prints out the

spark git commit: [Core][minor] remove unused `visitedStages` in `DAGScheduler.stageDependsOn`

Repository: spark Updated Branches: refs/heads/master 8cb23a1f9 - 3b5aaa6a5 [Core][minor] remove unused `visitedStages` in `DAGScheduler.stageDependsOn` We define and update `visitedStages` in `DAGScheduler.stageDependsOn`, but never read it. So we can safely remove it. Author: Wenchen Fan

spark git commit: [SPARK-5313][Project Infra]: Create simple framework for highlighting changes introduced in a PR

Repository: spark Updated Branches: refs/heads/master dda4dedca - 8cb23a1f9 [SPARK-5313][Project Infra]: Create simple framework for highlighting changes introduced in a PR Built a simple framework with a `dev/tests` directory to house all pull request related tests. I've moved the two