spark git commit: Revert "[SPARK-13534][PYSPARK] Using Apache Arrow to increase performance of DataFrame.toPandas"

2017-06-27 Thread wenchen
Repository: spark Updated Branches: refs/heads/master e793bf248 -> 838effb98 Revert "[SPARK-13534][PYSPARK] Using Apache Arrow to increase performance of DataFrame.toPandas" This reverts commit e44697606f429b01808c1a22cb44cb5b89585c5c. Project: http://git-wip-us.apache.org/repos/asf/spark/r

spark git commit: [SPARK-20889][SPARKR] Grouped documentation for MATH column methods

2017-06-27 Thread felixcheung
Repository: spark Updated Branches: refs/heads/master 2d686a19e -> e793bf248 [SPARK-20889][SPARKR] Grouped documentation for MATH column methods ## What changes were proposed in this pull request? Grouped documentation for math column methods. Author: actuaryzhang Author: Wayne Zhang Clos

spark git commit: [SPARK-21155][WEBUI] Add (? running tasks) into Spark UI progress

2017-06-27 Thread wenchen
Repository: spark Updated Branches: refs/heads/master fd8c931a3 -> 2d686a19e [SPARK-21155][WEBUI] Add (? running tasks) into Spark UI progress ## What changes were proposed in this pull request? Add metric on number of running tasks to status bar on Jobs / Active Jobs. ## How was this patch

spark git commit: [SPARK-19104][SQL] Lambda variables in ExternalMapToCatalyst should be global

2017-06-27 Thread wenchen
Repository: spark Updated Branches: refs/heads/branch-2.2 d8e3a4af3 -> 970f68c05 [SPARK-19104][SQL] Lambda variables in ExternalMapToCatalyst should be global The issue happens in `ExternalMapToCatalyst`. For example, the following codes create `ExternalMapToCatalyst` to convert Scala Map to

spark git commit: [SPARK-19104][SQL] Lambda variables in ExternalMapToCatalyst should be global

2017-06-27 Thread wenchen
Repository: spark Updated Branches: refs/heads/master b32bd005e -> fd8c931a3 [SPARK-19104][SQL] Lambda variables in ExternalMapToCatalyst should be global ## What changes were proposed in this pull request? The issue happens in `ExternalMapToCatalyst`. For example, the following codes create

spark git commit: [INFRA] Close stale PRs

2017-06-27 Thread srowen
Repository: spark Updated Branches: refs/heads/master 3cb3ccce1 -> b32bd005e [INFRA] Close stale PRs ## What changes were proposed in this pull request? This PR proposes to close stale PRs, mostly the same instances with https://github.com/apache/spark/pull/18017 I believe the author in #14

spark git commit: [SPARK-21196] Split codegen info of query plan into sequence

2017-06-27 Thread wenchen
Repository: spark Updated Branches: refs/heads/master c22810004 -> 3cb3ccce1 [SPARK-21196] Split codegen info of query plan into sequence codegen info of query plan can be very long. In debugging console / web page, it would be more readable if the subtrees and corresponding codegen are split