spark git commit: [SPARK-18811] StreamSource resolution should happen in stream execution thread

2016-12-09 Thread zsxwing
Repository: spark Updated Branches: refs/heads/branch-2.1 8bf56cc46 -> b020ce408 [SPARK-18811] StreamSource resolution should happen in stream execution thread ## What changes were proposed in this pull request? When you start a stream, if we are trying to resolve the source of the stream,

spark git commit: [SPARK-18811] StreamSource resolution should happen in stream execution thread

2016-12-09 Thread zsxwing
Repository: spark Updated Branches: refs/heads/master 3e11d5bfe -> 63c915987 [SPARK-18811] StreamSource resolution should happen in stream execution thread ## What changes were proposed in this pull request? When you start a stream, if we are trying to resolve the source of the stream, for

spark git commit: [SPARK-18807][SPARKR] Should suppress output print for calls to JVM methods with void return values

2016-12-09 Thread shivaram
Repository: spark Updated Branches: refs/heads/branch-2.1 e45345d91 -> 8bf56cc46 [SPARK-18807][SPARKR] Should suppress output print for calls to JVM methods with void return values ## What changes were proposed in this pull request? Several SparkR API calling into JVM methods that have void

spark git commit: [SPARK-18807][SPARKR] Should suppress output print for calls to JVM methods with void return values

2016-12-09 Thread shivaram
Repository: spark Updated Branches: refs/heads/master d2493a203 -> 3e11d5bfe [SPARK-18807][SPARKR] Should suppress output print for calls to JVM methods with void return values ## What changes were proposed in this pull request? Several SparkR API calling into JVM methods that have void

spark git commit: [SPARK-18812][MLLIB] explain "Spark ML"

2016-12-09 Thread meng
Repository: spark Updated Branches: refs/heads/branch-2.1 562507ef0 -> e45345d91 [SPARK-18812][MLLIB] explain "Spark ML" ## What changes were proposed in this pull request? There has been some confusion around "Spark ML" vs. "MLlib". This PR adds some FAQ-like entries to the MLlib user

spark git commit: [SPARK-18812][MLLIB] explain "Spark ML"

2016-12-09 Thread meng
Repository: spark Updated Branches: refs/heads/master cf33a8628 -> d2493a203 [SPARK-18812][MLLIB] explain "Spark ML" ## What changes were proposed in this pull request? There has been some confusion around "Spark ML" vs. "MLlib". This PR adds some FAQ-like entries to the MLlib user guide to

spark git commit: [SPARK-4105] retry the fetch or stage if shuffle block is corrupt

2016-12-09 Thread zsxwing
Repository: spark Updated Branches: refs/heads/master d60ab5fd9 -> cf33a8628 [SPARK-4105] retry the fetch or stage if shuffle block is corrupt ## What changes were proposed in this pull request? There is an outstanding issue that existed for a long time: Sometimes the shuffle blocks are

spark git commit: [SPARK-18745][SQL] Fix signed integer overflow due to toInt cast

2016-12-09 Thread hvanhovell
Repository: spark Updated Branches: refs/heads/branch-2.1 eb2d9bfd4 -> 562507ef0 [SPARK-18745][SQL] Fix signed integer overflow due to toInt cast ## What changes were proposed in this pull request? This PR avoids that a result of a cast `toInt` is negative due to signed integer overflow

spark git commit: [SPARK-18745][SQL] Fix signed integer overflow due to toInt cast

2016-12-09 Thread hvanhovell
Repository: spark Updated Branches: refs/heads/branch-2.0 65b4b0561 -> 2c342e5a4 [SPARK-18745][SQL] Fix signed integer overflow due to toInt cast ## What changes were proposed in this pull request? This PR avoids that a result of a cast `toInt` is negative due to signed integer overflow

spark git commit: [SPARK-18745][SQL] Fix signed integer overflow due to toInt cast

2016-12-09 Thread hvanhovell
Repository: spark Updated Branches: refs/heads/master b08b50045 -> d60ab5fd9 [SPARK-18745][SQL] Fix signed integer overflow due to toInt cast ## What changes were proposed in this pull request? This PR avoids that a result of a cast `toInt` is negative due to signed integer overflow (e.g.

spark git commit: [SPARK-18620][STREAMING][KINESIS] Flatten input rates in timeline for streaming + kinesis

2016-12-09 Thread srowen
Repository: spark Updated Branches: refs/heads/master be5fc6ef7 -> b08b50045 [SPARK-18620][STREAMING][KINESIS] Flatten input rates in timeline for streaming + kinesis ## What changes were proposed in this pull request? This pr is to make input rates in timeline more flat for spark streaming

[2/2] spark-website git commit: html changes for mllib site

2016-12-09 Thread jkbradley
html changes for mllib site Project: http://git-wip-us.apache.org/repos/asf/spark-website/repo Commit: http://git-wip-us.apache.org/repos/asf/spark-website/commit/a82adf04 Tree: http://git-wip-us.apache.org/repos/asf/spark-website/tree/a82adf04 Diff:

[1/2] spark-website git commit: updated MLlib site for 2.1

2016-12-09 Thread jkbradley
Repository: spark-website Updated Branches: refs/heads/asf-site 8d5d77c65 -> a82adf043 updated MLlib site for 2.1 Project: http://git-wip-us.apache.org/repos/asf/spark-website/repo Commit: http://git-wip-us.apache.org/repos/asf/spark-website/commit/057cad18 Tree:

spark git commit: [MINOR][SPARKR] Fix SparkR regex in copy command

2016-12-09 Thread shivaram
Repository: spark Updated Branches: refs/heads/master fd48d80a6 -> be5fc6ef7 [MINOR][SPARKR] Fix SparkR regex in copy command Fix SparkR package copy regex. The existing code leads to ``` Copying release tarballs to

spark git commit: [MINOR][SPARKR] Fix SparkR regex in copy command

2016-12-09 Thread shivaram
Repository: spark Updated Branches: refs/heads/branch-2.1 0c6415aec -> eb2d9bfd4 [MINOR][SPARKR] Fix SparkR regex in copy command Fix SparkR package copy regex. The existing code leads to ``` Copying release tarballs to

spark git commit: [SPARK-17822][R] Make JVMObjectTracker a member variable of RBackend

2016-12-09 Thread meng
Repository: spark Updated Branches: refs/heads/branch-2.0 44df6d2ce -> 65b4b0561 [SPARK-17822][R] Make JVMObjectTracker a member variable of RBackend ## What changes were proposed in this pull request? * This PR changes `JVMObjectTracker` from `object` to `class` and let its instance

spark git commit: [SPARK-17822][R] Make JVMObjectTracker a member variable of RBackend

2016-12-09 Thread meng
Repository: spark Updated Branches: refs/heads/branch-2.1 b226f10e3 -> 0c6415aec [SPARK-17822][R] Make JVMObjectTracker a member variable of RBackend ## What changes were proposed in this pull request? * This PR changes `JVMObjectTracker` from `object` to `class` and let its instance

spark git commit: [SPARK-17822][R] Make JVMObjectTracker a member variable of RBackend

2016-12-09 Thread meng
Repository: spark Updated Branches: refs/heads/master b162cc0c2 -> fd48d80a6 [SPARK-17822][R] Make JVMObjectTracker a member variable of RBackend ## What changes were proposed in this pull request? * This PR changes `JVMObjectTracker` from `object` to `class` and let its instance associated

spark git commit: [MINOR][CORE][SQL][DOCS] Typo fixes

2016-12-09 Thread srowen
Repository: spark Updated Branches: refs/heads/branch-2.1 72bf51997 -> b226f10e3 [MINOR][CORE][SQL][DOCS] Typo fixes ## What changes were proposed in this pull request? Typo fixes ## How was this patch tested? Local build. Awaiting the official build. Author: Jacek Laskowski

spark git commit: [MINOR][CORE][SQL][DOCS] Typo fixes

2016-12-09 Thread srowen
Repository: spark Updated Branches: refs/heads/master 67587d961 -> b162cc0c2 [MINOR][CORE][SQL][DOCS] Typo fixes ## What changes were proposed in this pull request? Typo fixes ## How was this patch tested? Local build. Awaiting the official build. Author: Jacek Laskowski

spark git commit: [SPARK-18637][SQL] Stateful UDF should be considered as nondeterministic

2016-12-09 Thread wenchen
Repository: spark Updated Branches: refs/heads/branch-2.1 2c88e1dc3 -> 72bf51997 [SPARK-18637][SQL] Stateful UDF should be considered as nondeterministic Make stateful udf as nondeterministic Add new test cases with both Stateful and Stateless UDF. Without the patch, the test cases will

spark git commit: [SPARK-18637][SQL] Stateful UDF should be considered as nondeterministic

2016-12-09 Thread wenchen
Repository: spark Updated Branches: refs/heads/master c074c96dc -> 67587d961 [SPARK-18637][SQL] Stateful UDF should be considered as nondeterministic ## What changes were proposed in this pull request? Make stateful udf as nondeterministic ## How was this patch tested? Add new test cases