Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9327#issuecomment-152098323
**[Test build #44578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44578/consoleFull)**
for PR 9327 at commit
[`85dadbc`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152098188
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/9241#issuecomment-152098120
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9327#issuecomment-152098139
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152098190
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9327#issuecomment-152098119
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9241#issuecomment-152098140
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152098100
**[Test build #44563 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44563/consoleFull)**
for PR 9326 at commit
[`fb70954`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9315#issuecomment-152098050
**[Test build #44576 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44576/consoleFull)**
for PR 9315 at commit
[`5bfab45`](https://gith
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9327#issuecomment-152098099
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
e
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152097828
Thanks for the review. Will merge this to master pending Jenkins.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9348#issuecomment-152097542
**[Test build #44575 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44575/consoleFull)**
for PR 9348 at commit
[`8e77826`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152097182
**[Test build #44577 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44577/consoleFull)**
for PR 9305 at commit
[`831d1c9`](https://gith
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/9308#discussion_r43353616
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala
---
@@ -1870,4 +1870,19 @@ class SQLQuerySuite extends QueryTest with
SharedSQ
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9315#issuecomment-152097112
Merged build started.
---
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
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9348#discussion_r43353538
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -417,6 +417,14 @@ object NullPropagation extends Rule[
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152097089
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9315#issuecomment-152097085
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152097111
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9351#issuecomment-152096373
**[Test build #44574 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44574/consoleFull)**
for PR 9351 at commit
[`ab4276f`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9348#issuecomment-152096399
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9348#issuecomment-152096387
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152096230
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152096229
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9348#issuecomment-152096139
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
e
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152096108
**[Test build #44562 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44562/consoleFull)**
for PR 9326 at commit
[`5ed1429`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9330#issuecomment-152095757
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/9330#issuecomment-152095758
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9330#issuecomment-152095675
**[Test build #44560 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44560/consoleFull)**
for PR 9330 at commit
[`28f959c`](https://git
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-152095666
You could create dataframe per path and then union them.
On Oct 28, 2015 19:14, "Jon Edvald" wrote:
> Hey all. Just ran into this bug when upgrading to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9346#issuecomment-152095222
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9346#issuecomment-152095218
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/9346#issuecomment-152094846
**[Test build #44559 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44559/consoleFull)**
for PR 9346 at commit
[`9be67c8`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9351#issuecomment-152094813
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9351#issuecomment-152094900
Merged build started.
---
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
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/8587#discussion_r43352853
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/functions.scala
---
@@ -524,6 +525,116 @@ case class Sum(child: Expr
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9350#issuecomment-152094171
**[Test build #44573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44573/consoleFull)**
for PR 9350 at commit
[`337eef6`](https://gith
Github user watermen commented on the pull request:
https://github.com/apache/spark/pull/9349#issuecomment-152094274
retest 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 fe
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/9351
[SPARK-11400][SQL] BroadcastNestedLoopJoin should support LeftSemi join
JIRA: https://issues.apache.org/jira/browse/SPARK-11400
BroadcastNestedLoopJoin doesn't support LeftSemi join now. We s
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9350#issuecomment-152092650
Merged build triggered.
---
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 h
Github user watermen commented on the pull request:
https://github.com/apache/spark/pull/9349#issuecomment-152092774
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 feat
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152092666
@pravingadakh I perfer to use the existing example code. @mengxr What is
your opinion?
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9350#issuecomment-152092670
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9349#issuecomment-152092653
Can one of the admins verify this patch?
---
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 pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152092320
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/9340#issuecomment-152092324
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152092145
**[Test build #44571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44571/consoleFull)**
for PR 9340 at commit
[`fb0050b`](https://git
GitHub user maropu opened a pull request:
https://github.com/apache/spark/pull/9350
[SPARK-11394][SQL] Throw IllegalArgumentException for unsupported types in
postgresql
If DataFrame has BYTE types, throws an exception:
org.postgresql.util.PSQLException: ERROR: type "byte" does
GitHub user wzhfy opened a pull request:
https://github.com/apache/spark/pull/9349
[SPARK-11398][SQL] misleading dialect conf at the start of spark-sql
Instead of overriding def dialect in conf of HiveContext, I set the
SQLConf.DIALECT directly as "hiveql", such that result of "set
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/9207#issuecomment-152091359
re-ping @jkbradley
---
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 pravingadakh commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152090442
@yinxusen I will do the changes mentioned. I am confused about one thing
though, FPGrowth examples are already available in scala and java language, and
it's conten
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9340#discussion_r43352214
--- Diff: examples/src/main/python/mllib/fpgrowth_example.py ---
@@ -0,0 +1,28 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9276#issuecomment-152089755
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9241#issuecomment-152089767
**[Test build #44572 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44572/consoleFull)**
for PR 9241 at commit
[`a3e01d0`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9276#issuecomment-152089754
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/9276#issuecomment-152089722
**[Test build #44561 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44561/consoleFull)**
for PR 9276 at commit
[`2130068`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9241#issuecomment-152089469
**[Test build #1960 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1960/consoleFull)**
for PR 9241 at commit
[`0971d27`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9241#issuecomment-152089228
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9241#issuecomment-152089158
Merged build triggered.
---
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-152088973
/cc @davies @andrewor14 for review. This is still WIP pending some tests,
but the high-level design is ready for comments. I've posted a PR description
to help guide y
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9340#discussion_r43352124
--- Diff:
examples/src/main/java/org/apache/spark/examples/mllib/JavaPrefixSpanExample.java
---
@@ -0,0 +1,50 @@
+/*
+ * Licensed to the Apache Soft
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9340#discussion_r43352105
--- Diff:
examples/src/main/java/org/apache/spark/examples/mllib/JavaAssociationRulesExample.java
---
@@ -0,0 +1,49 @@
+/*
+ * Licensed to the Apach
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152088613
@liancheng Thanks, LGTM.
---
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 thi
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152087569
@pravingadakh You need to label `$example on$` and `$example off$` in
comments of example codes. Otherwise, the include_example cannot trim the code
snippt out. Example
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-152087085
**[Test build #44570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44570/consoleFull)**
for PR 9344 at commit
[`eb3180a`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-152087097
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-152087094
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/9340#issuecomment-152087056
**[Test build #44571 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44571/consoleFull)**
for PR 9340 at commit
[`fb0050b`](https://gith
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152086887
Just checked spark-csv and spark-avro, both conform to this assumption.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152086609
@davies I don't think so. Third-party `HadoopFsRelation` data sources only
overrides `buildScan` and always return RDDs containing external `Row`. The
`buildInternalSc
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-152085955
**[Test build #44570 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44570/consoleFull)**
for PR 9344 at commit
[`eb3180a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-152085683
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152085696
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-152085697
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152085688
Merged build triggered.
---
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9241#issuecomment-152085503
**[Test build #44569 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44569/consoleFull)**
for PR 9241 at commit
[`0971d27`](https://gith
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152085390
@liancheng Will this break any third-party data sources?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152085213
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
enab
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9340#issuecomment-152085195
@pravingadakh Could you update the PR title to make it more specific?
@yinxusen Could you review this PR?
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9241#issuecomment-152085212
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9241#issuecomment-152085173
Merged build triggered.
---
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152082877
**[Test build #44568 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44568/consoleFull)**
for PR 9326 at commit
[`88edd14`](https://gith
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/9313#issuecomment-152082830
@sryza it does not, we could make it a flag so the default behaviour is
more consistent, although this behaviour is in line with addPyFile which does
add the file to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9313#issuecomment-152082837
**[Test build #44567 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44567/consoleFull)**
for PR 9313 at commit
[`a0fdddb`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9347#issuecomment-152082734
**[Test build #44566 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44566/consoleFull)**
for PR 9347 at commit
[`c684a7b`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152082468
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152082460
Merged build triggered.
---
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 h
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/9313#discussion_r43350809
--- Diff: python/pyspark/context.py ---
@@ -806,6 +806,24 @@ def addPyFile(self, path):
import importlib
importlib.invalidate
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9347#issuecomment-152081998
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9313#issuecomment-152081988
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9347#issuecomment-152081986
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9313#issuecomment-152081997
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9347#issuecomment-152081931
**[Test build #44565 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44565/consoleFull)**
for PR 9347 at commit
[`7c595fd`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152080921
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9326#issuecomment-152080917
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/9326#issuecomment-152080910
**[Test build #44564 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44564/consoleFull)**
for PR 9326 at commit
[`3f25d6a`](https://git
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9305#issuecomment-152081103
overall looks good to me. @davies do you want to do the final sign-off?
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9347#issuecomment-152080579
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9348#issuecomment-152080554
Can one of the admins verify this patch?
---
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 pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9347#issuecomment-152080556
Merged build triggered.
---
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 h
1 - 100 of 721 matches
Mail list logo
