Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-154658079
**[Test build #45281 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45281/consoleFull)**
for PR 9488 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154660094
**[Test build #45280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45280/consoleFull)**
for PR 9536 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154660141
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9529#issuecomment-154707638
This seems like such a straightforward doc fix that I'm going to merge it.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9540#issuecomment-154709676
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-154712523
@gliptak you can ignore that, it's indeed a false positive. The problem is
the compilation error. Yes, the problem is the SBT build, not Maven, as
expected. You'd have
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/9541
[SPARK-9241][SQL] Supporting multiple DISTINCT columns - follow-up
This PR is a follow up for PR https://github.com/apache/spark/pull/9406. It
adds more documentation to the rewriting rule,
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9409#discussion_r44213448
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -419,3 +419,30 @@ case class
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9538#discussion_r44212577
--- Diff: core/src/main/scala/org/apache/spark/storage/RDDInfo.scala ---
@@ -28,20 +28,10 @@ class RDDInfo(
val numPartitions: Int,
var
GitHub user mindprince opened a pull request:
https://github.com/apache/spark/pull/9540
[DOC] [SQL] Remove redundant out-of-place python snippet
This snippet seems to be mistakenly introduced at two places in #5348.
You can merge this pull request into a Git repository by running:
Github user mindprince commented on the pull request:
https://github.com/apache/spark/pull/9540#issuecomment-154709554
cc - @liancheng
---
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/9538#issuecomment-154712870
**[Test build #45283 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45283/consoleFull)**
for PR 9538 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154715366
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154716428
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154716423
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
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154695463
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154702642
**[Test build #45283 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45283/consoleFull)**
for PR 9538 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154716392
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
Github user yueqianzhu closed the pull request at:
https://github.com/apache/spark/pull/9515
---
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
Github user tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/9344#discussion_r44212193
--- Diff:
core/src/main/scala/org/apache/spark/memory/ExecutionMemoryPool.scala ---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the Apache Software
GitHub user agsachin opened a pull request:
https://github.com/apache/spark/pull/9539
[SPARK-11552][DOCS][Replaced example code in ml-decision-tree.md using
include_example]
I have tested it on my local, it is working fine, please review
You can merge this pull request into a Git
Github user tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/9344#discussion_r44212241
--- Diff:
core/src/main/scala/org/apache/spark/memory/ExecutionMemoryPool.scala ---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the Apache Software
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9523#issuecomment-154707614
Yeah I meant these things all already generate a warning. I tend to agree
with your additional change for this JIRA. Any other opinions?
---
If your project is set up
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154707778
It worked fine for me.
```
â spark git:(master) â ./build/mvn -Pyarn -Phadoop-2.6
-Dhadoop.version=2.7.1 -Dscala-2.11 -Phive -Phive-thriftserver
Github user gliptak commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-154712261
@srowen From SparkQA: "This patch adds the following public classes
(experimental):" I do not see how my change adds a public class ...
As for the compile error, it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154712895
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154716268
add to whitelist
---
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/9409#issuecomment-154716609
**[Test build #2004 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2004/consoleFull)**
for PR 9409 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154699687
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154699714
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
GitHub user tedyu opened a pull request:
https://github.com/apache/spark/pull/9538
Fix Scala 2.11 compilation error in RDDInfo.scala
As shown in
https://amplab.cs.berkeley.edu/jenkins/view/Spark-QA-Compile/job/Spark-Master-Scala211-Compile/1946/console
, compilation fails with:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9539#issuecomment-154704021
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
Github user tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/9344#discussion_r44212316
--- Diff: core/src/main/scala/org/apache/spark/memory/MemoryPool.scala ---
@@ -0,0 +1,71 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154707413
CC @andrewor14 /
https://github.com/apache/spark/commit/7f741905b06ed6d3dfbff6db41a3355dab71aa3c
@tedyu you should probably attach this to SPARK-2
---
If your
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9540#discussion_r44212912
--- Diff: docs/sql-programming-guide.md ---
@@ -1089,15 +1089,6 @@ for (teenName in collect(teenNames)) {
-
--- End diff --
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154716913
**[Test build #45284 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45284/consoleFull)**
for PR 9541 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9531#discussion_r44209587
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/DataFrame.scala ---
@@ -1478,18 +1478,54 @@ class DataFrame private[sql](
/**
*
Github user cloud-fan closed the pull request at:
https://github.com/apache/spark/pull/9358
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9537#issuecomment-154665282
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
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9531#discussion_r44209647
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/DataFrame.scala ---
@@ -1478,18 +1478,54 @@ class DataFrame private[sql](
/**
*
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-154672307
**[Test build #45278 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45278/consoleFull)**
for PR 9524 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154671582
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154671451
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-154672657
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154657201
**[Test build #45280 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45280/consoleFull)**
for PR 9536 at commit
GitHub user somideshmukh opened a pull request:
https://github.com/apache/spark/pull/9537
[SPARK-11551][DOC][Example]Replace example code in ml-features.md using
include_example
Replaced Java and Scala code
You can merge this pull request into a Git repository by running:
$
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-154682904
**[Test build #2003 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2003/consoleFull)**
for PR 9488 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154683247
**[Test build #45282 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45282/consoleFull)**
for PR 9536 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154683477
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-154690848
**[Test build #45281 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45281/consoleFull)**
for PR 9488 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-154690869
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
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9531#discussion_r44209605
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/DataFrame.scala ---
@@ -1478,18 +1478,54 @@ class DataFrame private[sql](
/**
*
Github user DoingDone9 commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-154654481
@navis
when i use spark-sql and run sql like that
"
add jar /home/udf-0.0.1-SNAPSHOT.jar;
create temporary function arr_greater_equal as
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9523#issuecomment-154689758
Looking at the code again, looks like there's already some codes take care
of this backward compatibility in yarn
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9409#discussion_r44210935
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -419,3 +419,30 @@ case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-154656407
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-154656424
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-154653067
Eh, the line you changed doesn't compile. It seems quite directly related!
But yes the question is why indeed. Does it compile for you with Maven? then we
may have a
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9531#issuecomment-154655582
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 this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154655609
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154655618
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
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9523#issuecomment-154665578
Ahhh, very sorry I misunderstood this PR. Yes, it is my bad to ignore this
command line argument (`--num-executors`) which also can set executor number.
Looks like in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9536#issuecomment-154679800
**[Test build #45282 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45282/consoleFull)**
for PR 9536 at commit
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r44213675
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.scala
---
@@ -351,6 +351,50 @@ class PairDStreamFunctions[K,
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r44213622
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/EmittedRecordsDStream.scala
---
@@ -0,0 +1,114 @@
+/*
+ * Licensed to the
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/9538#issuecomment-154719077
MiMA check 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 not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9496#issuecomment-154722401
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9496#issuecomment-154722399
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154722400
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154723564
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154723585
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-154738601
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-154738590
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9496#issuecomment-154740621
**[Test build #45287 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45287/consoleFull)**
for PR 9496 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9472#issuecomment-154740564
**[Test build #45290 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45290/consoleFull)**
for PR 9472 at commit
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9092#discussion_r44216481
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/feature/TokenizerSuite.scala ---
@@ -69,6 +69,18 @@ class RegexTokenizerSuite extends SparkFunSuite with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9451#issuecomment-154743558
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9451#issuecomment-154743562
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
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9409#discussion_r44216923
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/Utils.scala
---
@@ -54,10 +54,14 @@ object Utils {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9472#issuecomment-154751482
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9472#issuecomment-154751470
**[Test build #45290 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45290/consoleFull)**
for PR 9472 at commit
Github user reggert commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-154751770
I've added some unit tests that verify that my changes, do, indeed, stop
callbacks from consuming threads before the jobs have completed.
---
If your project is set up
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9451#issuecomment-154752182
**[Test build #45291 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45291/consoleFull)**
for PR 9451 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9451#issuecomment-154752200
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154752218
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154752499
hmm... seems jenkins did not pick up this pr.
---
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
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154752963
This one is currently running:
https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2005/consoleFull
---
If your project is set up for it, you can
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154753467
oh, right, I pasted the wrong link.
---
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 CharlesYeh commented on the pull request:
https://github.com/apache/spark/pull/9472#issuecomment-154753882
I don't think I made changes relevant to the tests..
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154742112
**[Test build #45288 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45288/consoleFull)**
for PR 9541 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154742161
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
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9092#issuecomment-154743585
I'm wondering now if we should set it to convert to lowercase by default.
I know it breaks behavior, but otherwise, we'll introduce an inconsistency in
the API
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9451#issuecomment-154743895
**[Test build #45291 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45291/consoleFull)**
for PR 9451 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-154748281
**[Test build #45289 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45289/consoleFull)**
for PR 9524 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-154748475
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154752165
**[Test build #2005 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2005/consoleFull)**
for PR 9409 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154752585
Hope
https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2003/ can
finish without any problem.
---
If your project is set up for it, you can reply to
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-154752998
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9541#issuecomment-154753581
LGTM. Merging to master and 1.6 branch.
---
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/9530#issuecomment-154753512
**[Test build #45292 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45292/consoleFull)**
for PR 9530 at commit
1 - 100 of 196 matches
Mail list logo
