spark git commit: [SPARK-20401][DOC] In the spark official configuration document, the 'spark.driver.supervise' configuration parameter specification and default values are necessary.

2017-04-21 Thread srowen
Repository: spark Updated Branches: refs/heads/branch-2.2 ff1f989f2 -> 6c2489c66 [SPARK-20401][DOC] In the spark official configuration document, the 'spark.driver.supervise' configuration parameter specification and default values are necessary. ## What changes were proposed in this pull

spark git commit: [SPARK-20401][DOC] In the spark official configuration document, the 'spark.driver.supervise' configuration parameter specification and default values are necessary.

2017-04-21 Thread srowen
Repository: spark Updated Branches: refs/heads/master fd648bff6 -> ad290402a [SPARK-20401][DOC] In the spark official configuration document, the 'spark.driver.supervise' configuration parameter specification and default values are necessary. ## What changes were proposed in this pull

spark git commit: [SPARK-20371][R] Add wrappers for collect_list and collect_set

2017-04-21 Thread felixcheung
Repository: spark Updated Branches: refs/heads/master eb00378f0 -> fd648bff6 [SPARK-20371][R] Add wrappers for collect_list and collect_set ## What changes were proposed in this pull request? Adds wrappers for `collect_list` and `collect_set`. ## How was this patch tested? Unit tests,

spark git commit: [SPARK-20423][ML] fix MLOR coeffs centering when reg == 0

2017-04-21 Thread dbtsai
Repository: spark Updated Branches: refs/heads/branch-2.2 adaa3f7e0 -> ff1f989f2 [SPARK-20423][ML] fix MLOR coeffs centering when reg == 0 ## What changes were proposed in this pull request? When reg == 0, MLOR has multiple solutions and we need to centralize the coeffs to get identical

spark git commit: [SPARK-20423][ML] fix MLOR coeffs centering when reg == 0

2017-04-21 Thread dbtsai
Repository: spark Updated Branches: refs/heads/master a750a5959 -> eb00378f0 [SPARK-20423][ML] fix MLOR coeffs centering when reg == 0 ## What changes were proposed in this pull request? When reg == 0, MLOR has multiple solutions and we need to centralize the coeffs to get identical result.

spark git commit: [SPARK-20341][SQL] Support BigInt's value that does not fit in long value range

2017-04-21 Thread wenchen
Repository: spark Updated Branches: refs/heads/branch-2.2 aaeca8bdd -> adaa3f7e0 [SPARK-20341][SQL] Support BigInt's value that does not fit in long value range ## What changes were proposed in this pull request? This PR avoids an exception in the case where `scala.math.BigInt` has a value

spark git commit: [SPARK-20341][SQL] Support BigInt's value that does not fit in long value range

2017-04-21 Thread wenchen
Repository: spark Updated Branches: refs/heads/master c9e6035e1 -> a750a5959 [SPARK-20341][SQL] Support BigInt's value that does not fit in long value range ## What changes were proposed in this pull request? This PR avoids an exception in the case where `scala.math.BigInt` has a value that

spark git commit: [SPARK-20412] Throw ParseException from visitNonOptionalPartitionSpec instead of returning null values.

2017-04-21 Thread wenchen
Repository: spark Updated Branches: refs/heads/branch-2.2 eb4d097c3 -> aaeca8bdd [SPARK-20412] Throw ParseException from visitNonOptionalPartitionSpec instead of returning null values. ## What changes were proposed in this pull request? If a partitionSpec is supposed to not contain optional

spark git commit: [SPARK-20412] Throw ParseException from visitNonOptionalPartitionSpec instead of returning null values.

2017-04-21 Thread wenchen
Repository: spark Updated Branches: refs/heads/master 34767997e -> c9e6035e1 [SPARK-20412] Throw ParseException from visitNonOptionalPartitionSpec instead of returning null values. ## What changes were proposed in this pull request? If a partitionSpec is supposed to not contain optional

spark git commit: Small rewording about history server use case

2017-04-21 Thread srowen
Repository: spark Updated Branches: refs/heads/branch-2.2 cddb4b7db -> eb4d097c3 Small rewording about history server use case Hello PR #10991 removed the built-in history view from Spark Standalone, so the history server is no longer useful to Yarn or Mesos only. Author: Hervé

spark git commit: Small rewording about history server use case

2017-04-21 Thread srowen
Repository: spark Updated Branches: refs/heads/branch-2.1 66e7a8f1d -> fb0351a3f Small rewording about history server use case Hello PR #10991 removed the built-in history view from Spark Standalone, so the history server is no longer useful to Yarn or Mesos only. Author: Hervé

spark git commit: Small rewording about history server use case

2017-04-21 Thread srowen
Repository: spark Updated Branches: refs/heads/master e2b3d2367 -> 34767997e Small rewording about history server use case Hello PR #10991 removed the built-in history view from Spark Standalone, so the history server is no longer useful to Yarn or Mesos only. Author: Hervé

spark git commit: [SPARK-20420][SQL] Add events to the external catalog

2017-04-21 Thread rxin
Repository: spark Updated Branches: refs/heads/master 48d760d02 -> e2b3d2367 [SPARK-20420][SQL] Add events to the external catalog ## What changes were proposed in this pull request? It is often useful to be able to track changes to the `ExternalCatalog`. This PR makes the `ExternalCatalog`

spark git commit: [SPARK-20420][SQL] Add events to the external catalog

2017-04-21 Thread rxin
Repository: spark Updated Branches: refs/heads/branch-2.2 6cd2f16b1 -> cddb4b7db [SPARK-20420][SQL] Add events to the external catalog ## What changes were proposed in this pull request? It is often useful to be able to track changes to the `ExternalCatalog`. This PR makes the