Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6291#issuecomment-156948783
**[Test build #45987 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45987/consoleFull)**
for PR 6291 at commit
[`31ba5de`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9727#issuecomment-156946531
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9727#issuecomment-156946533
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9727#issuecomment-156946466
**[Test build #45985 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45985/consoleFull)**
for PR 9727 at commit
[`f311637`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156946393
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156946392
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156946318
**[Test build #45977 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45977/consoleFull)**
for PR 9542 at commit
[`eeaa6b6`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9726#issuecomment-156945880
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user somideshmukh commented on the pull request:
https://github.com/apache/spark/pull/9537#issuecomment-156945905
I am working on this,today it will be completed
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9726#issuecomment-156945881
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9726#issuecomment-156945797
**[Test build #45980 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45980/consoleFull)**
for PR 9726 at commit
[`6dbc124`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9728#issuecomment-156945569
**[Test build #45986 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45986/consoleFull)**
for PR 9728 at commit
[`afc9664`](https://gith
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9728#issuecomment-156944206
cc @davies
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156944153
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9728
[SPARK-11752][SQL] fix timezone problem for DateTimeUtils.getSeconds
code snippet to reproduce it:
```
TimeZone.setDefault(TimeZone.getTimeZone("Asia/Shanghai"))
val t = Timestamp.value
Github user archit279thakur commented on the pull request:
https://github.com/apache/spark/pull/6263#issuecomment-156944200
It says: Error: Invalid or corrupt jarfile build/sbt-launch-0.13.7.jar
Should I bring it up to date with master first?
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156944154
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156944117
**[Test build #45979 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45979/consoleFull)**
for PR 9542 at commit
[`eeaa6b6`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9727#issuecomment-156944124
**[Test build #45985 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45985/consoleFull)**
for PR 9727 at commit
[`f311637`](https://gith
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9717#issuecomment-156943032
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
en
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/9727
[SPARK-11684] [R] [ML] [Doc] Update SparkR glm API doc, user guide and
example codes
Update SparkR glm API doc, user guide and example codes.
You can merge this pull request into a Git repositor
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8923#issuecomment-156942598
Build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does n
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8923#issuecomment-156942359
[Test build #45975 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45975/console)
for PR 8923 at commit
[`d747d51`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6263#issuecomment-156941074
[Test build #45984 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45984/consoleFull)
for PR 6263 at commit
[`cef7c8b`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6263#issuecomment-156941081
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6263#issuecomment-156941079
Build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does n
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6263#issuecomment-156940725
[Test build #45984 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45984/consoleFull)
for PR 6263 at commit
[`cef7c8b`](https://gith
Github user archit279thakur commented on the pull request:
https://github.com/apache/spark/pull/6263#issuecomment-156940368
jenkins, please test again.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156939716
**[Test build #45983 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45983/consoleFull)**
for PR 9652 at commit
[`e69c538`](https://gith
Github user archit279thakur commented on a diff in the pull request:
https://github.com/apache/spark/pull/6263#discussion_r44892842
--- Diff:
core/src/main/scala/org/apache/spark/storage/StorageStatusListener.scala ---
@@ -28,15 +36,33 @@ import org.apache.spark.scheduler._
*
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156936688
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156936689
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9723#issuecomment-156936613
I'm going to revert those commits now to try to unbreak the SBT builds.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156936655
**[Test build #45982 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45982/consoleFull)**
for PR 9652 at commit
[`85d4e3d`](https://git
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9723#issuecomment-156935359
IMO, we should revert
https://github.com/apache/spark/commit/3e0a6cf1e02a19b37c68d3026415d53bb57a576b
The user should not call `stop` or other long-time work in
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9724#issuecomment-156930634
LGTM pending jenkins.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fe
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/9652#discussion_r44891774
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonSuite.scala
---
@@ -1393,4 +1399,51 @@ class JsonSuite extends Quer
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156927078
**[Test build #45982 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45982/consoleFull)**
for PR 9652 at commit
[`85d4e3d`](https://gith
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/9652#discussion_r44891704
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -440,9 +441,16 @@ abstract class HadoopFsRelation
private[sql](may
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9724#issuecomment-156924453
**[Test build #45981 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45981/consoleFull)**
for PR 9724 at commit
[`d8ca56d`](https://gith
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-156922650
I did some more digging and it looks like this whole locking situation is a
much bigger mess than I originally estimated:
- SBT coordinates access to the Ivy c
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9724#issuecomment-156922706
Alright I've updated it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9726#issuecomment-156919553
**[Test build #45980 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45980/consoleFull)**
for PR 9726 at commit
[`6dbc124`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9701#issuecomment-156919277
**[Test build #2062 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2062/consoleFull)**
for PR 9701 at commit
[`fd34d86`](https://gi
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9726#issuecomment-156918831
cc @marmbrus
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featur
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9726#discussion_r44889853
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/objects.scala
---
@@ -288,14 +287,13 @@ case class WrapOption(optionType: D
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9726#discussion_r44889803
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -718,39 +630,4 @@ trait ScalaReflection {
thr
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9726
[SPARK-11750][SQL] revert SPARK-11727 and code clean up
After some experiment, I found it's not convenient to have separate encoder
builders: `FlatEncoder` and `ProductEncoder`. For example, when
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156917263
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156917265
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156917249
**[Test build #45978 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45978/consoleFull)**
for PR 9652 at commit
[`fba713a`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9720#issuecomment-156917038
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9720#issuecomment-156917037
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9720#issuecomment-156916982
**[Test build #45974 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45974/consoleFull)**
for PR 9720 at commit
[`5a5be06`](https://git
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9717
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156916753
**[Test build #45979 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45979/consoleFull)**
for PR 9542 at commit
[`eeaa6b6`](https://gith
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9717#issuecomment-156916653
Merging to master and branch 1.6.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156916431
test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156915756
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9717#issuecomment-156915791
LGTM cc @yhuai
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156915753
Build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does n
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156915725
**[Test build #45970 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45970/consoleFull)**
for PR 9542 at commit
[`83b1c77`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156915616
**[Test build #45978 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45978/consoleFull)**
for PR 9652 at commit
[`fba713a`](https://gith
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-156915513
Isn't `spark-submit`'s default behavior to use a shared Ivy cache? If so,
shouldn't we be testing with that as the default rather than the exception so
that any bugs w
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-156914641
@JoshRosen There are so many things I couldn't figure about Ivy... The
library is practically a black box. It unfortunately doesn't have a lot of
documentation (at least
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9542#issuecomment-156914531
**[Test build #45977 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45977/consoleFull)**
for PR 9542 at commit
[`eeaa6b6`](https://gith
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156914464
@liancheng can you also take a look?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does n
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-15691
ok to test
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabl
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9652#discussion_r44888758
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonSuite.scala
---
@@ -1393,4 +1399,51 @@ class JsonSuite extends QueryTest
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9652#discussion_r44888724
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonSuite.scala
---
@@ -1393,4 +1399,51 @@ class JsonSuite extends QueryTest
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9652#discussion_r44888648
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -440,9 +441,16 @@ abstract class HadoopFsRelation
private[sql](maybePart
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9652#discussion_r44888658
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonSuite.scala
---
@@ -17,10 +17,12 @@
package org.apache.spark.s
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9652#discussion_r44888542
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -440,9 +441,16 @@ abstract class HadoopFsRelation
private[sql](maybePart
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-156914028
@vanzin, I took a closer look and it appears that Ivy's default locking
strategy is "no locking", which is not safe when using a shared cache. I'm
going to submit a se
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9652#discussion_r44888551
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -440,9 +441,16 @@ abstract class HadoopFsRelation
private[sql](maybePart
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9724#issuecomment-156913770
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9724#issuecomment-156913773
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9724#issuecomment-156913465
**[Test build #45972 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45972/consoleFull)**
for PR 9724 at commit
[`00cfc19`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9725#issuecomment-156912408
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9725#issuecomment-156912410
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9725#issuecomment-156912342
**[Test build #45976 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45976/consoleFull)**
for PR 9725 at commit
[`7209ed1`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9724#issuecomment-156912020
**[Test build #2061 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2061/consoleFull)**
for PR 9724 at commit
[`00cfc19`](https://gi
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/9723#issuecomment-156911334
```
sbt.ForkMain$ForkError: Test failed with compression using codec
org.apache.spark.io.LZ4CompressionCodec:
assertion failed: expected groupByKey to spill, b
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9725#issuecomment-156911128
**[Test build #45976 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45976/consoleFull)**
for PR 9725 at commit
[`7209ed1`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9723#issuecomment-156910699
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9723#issuecomment-156910680
**[Test build #45973 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45973/consoleFull)**
for PR 9723 at commit
[`cd9b2f2`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9723#issuecomment-156910700
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8923#issuecomment-156910691
[Test build #45975 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45975/consoleFull)
for PR 8923 at commit
[`d747d51`](https://gith
GitHub user zjffdu opened a pull request:
https://github.com/apache/spark/pull/9725
[SPARK-11747][EXAMPLES] Can not specify input path in python
logistic_regression example under ml
You can merge this pull request into a Git repository by running:
$ git pull https://github.co
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9717#issuecomment-156910160
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9717#issuecomment-156910158
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9717#issuecomment-156910105
**[Test build #45969 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45969/consoleFull)**
for PR 9717 at commit
[`195d176`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9701#issuecomment-156906040
**[Test build #2062 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2062/consoleFull)**
for PR 9701 at commit
[`fd34d86`](https://git
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9712#discussion_r44886605
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/objects.scala
---
@@ -343,33 +343,50 @@ case class MapObjects(
private
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9390
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-156904096
Thanks @sun-rui and @brkyvz -- Sorry for the delay in getting to this.
LGTM. Merging this to master and branch-1.6
---
If your project is set up for it, you can reply
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9652#issuecomment-156903919
@yhuai Hello Yin, could you please take a look and give me your input.
Thanks a lot.
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9099
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-156901270
Thanks @zero323 and @sun-rui - Merging this
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proj
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9720#issuecomment-156901114
**[Test build #45974 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45974/consoleFull)**
for PR 9720 at commit
[`5a5be06`](https://gith
1 - 100 of 274 matches
Mail list logo
