Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9472#issuecomment-154350128
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/9503#issuecomment-154350451
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-154350428
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9519#issuecomment-154350423
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-154351785
[Test build #45214 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45214/consoleFull)
for PR 9503 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9270#discussion_r44117245
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/ScalaUDF.scala
---
@@ -965,6 +969,80 @@ case class ScalaUDF(
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9406#issuecomment-154352102
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/9406#issuecomment-154352052
**[Test build #45207 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45207/consoleFull)**
for PR 9406 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9143#issuecomment-154352789
**[Test build #45208 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45208/consoleFull)**
for PR 9143 at commit
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-154353494
Let me prepare couple of screenshots to illustrate the sort order.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9143#issuecomment-154353164
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-154353831
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-154353812
[Test build #45214 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45214/console)
for PR 9503 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9143#issuecomment-154353160
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-154356583
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/9503#issuecomment-154356522
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/7410#issuecomment-154359198
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-154360557
**[Test build #45215 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45215/consoleFull)**
for PR 9503 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-154360561
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-154360597
**[Test build #45216 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45216/consoleFull)**
for PR 7410 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-154360559
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/9297#issuecomment-154361228
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/9297#issuecomment-154361230
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9287#issuecomment-154364662
**[Test build #45217 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45217/consoleFull)**
for PR 9287 at commit
GitHub user hhbyyh opened a pull request:
https://github.com/apache/spark/pull/9520
[SPARK-11507] [MLlib] add compact in Matrices fromBreeze
jira: https://issues.apache.org/jira/browse/SPARK-11507
"In certain situations when adding two block matrices, I get an error
regarding
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9520#issuecomment-154366500
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/9344#issuecomment-154377070
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/9344#issuecomment-154377089
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/9520#issuecomment-154377374
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9520#issuecomment-154377270
**[Test build #45218 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45218/consoleFull)**
for PR 9520 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9520#issuecomment-154377373
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9468#issuecomment-154378200
**[Test build #45212 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45212/consoleFull)**
for PR 9468 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9468#issuecomment-154378538
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9468#issuecomment-154378537
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-154380899
**[Test build #45221 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45221/consoleFull)**
for PR 9344 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9414#issuecomment-154381079
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9414#issuecomment-154380928
**[Test build #45213 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45213/consoleFull)**
for PR 9414 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9414#issuecomment-154381081
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9008#issuecomment-154381876
[Test build #45206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45206/console)
for PR 9008 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9008#issuecomment-154381940
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9008#issuecomment-154381942
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user pravingadakh opened a pull request:
https://github.com/apache/spark/pull/9522
[SPARK-11535][ML] handling empty string in StringIndexer
Replacing "" (not null) with string "EMPTY_STRING" in StringIndexer.
Another approach is to use "0" (or next available integer), but it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9263#issuecomment-154479089
**[Test build #45227 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45227/consoleFull)**
for PR 9263 at commit
Github user hhbyyh commented on the pull request:
https://github.com/apache/spark/pull/9513#issuecomment-154480232
@jkbradley Thanks for looping me in and welcome back. I'll try to send some
feedback this weekend.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154383561
**[Test build #1996 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1996/consoleFull)**
for PR 9501 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9521#issuecomment-154388797
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/9521#issuecomment-154388703
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/9406#issuecomment-154398778
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9436#issuecomment-154398789
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/9406#issuecomment-154398663
**[Test build #45219 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45219/consoleFull)**
for PR 9406 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7841#issuecomment-154477941
@aray sorry was away for spark summit - back now and will get to this today.
---
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/9472#issuecomment-154479994
Build triggered. sha1 is original commit.
---
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/9472#issuecomment-154480025
Build started sha1 is original commit.
---
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/9089#issuecomment-154498875
Build started sha1 is merged.
---
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/9517#issuecomment-154498818
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
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/8643#discussion_r44172629
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/api/python/LDAModelWrapper.scala ---
@@ -0,0 +1,45 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-154498839
Build triggered. sha1 is merged.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154499244
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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9270#issuecomment-154499721
LGTM, merging this into 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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9143#discussion_r44173319
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -488,7 +491,12 @@ class ReceiverTracker(ssc:
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9143#discussion_r44173447
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -488,7 +491,12 @@ class ReceiverTracker(ssc:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9270
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9517#issuecomment-154501691
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 yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8563#issuecomment-154501697
@nilmeier thanks. This document would help you with contributing to Spark.
https://cwiki.apache.org/confluence/display/SPARK/Spark+Code+Style+Guide
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9517#issuecomment-154502425
**[Test build #45235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45235/consoleFull)**
for PR 9517 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154503830
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45234/
---
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9468#issuecomment-154503953
LGTM. 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154503826
Build finished. No test results found.
---
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/9525#issuecomment-154503795
Build started sha1 is merged.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9453
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154505090
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-154505864
Please don't use macros and quasiquotes. They are slow and not IDE
friendly. We replaced them with Janino in SQL.
---
If your project is set up for it, you can reply to
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/9525#issuecomment-154508219
I think it would be natural to fix the Scala error message and fix the
condition in Python. The algorithm checks not the indexes have duplicated
values, but the indexes
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9143#discussion_r44176718
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/util/BatchedWriteAheadLog.scala
---
@@ -0,0 +1,206 @@
+/*
+ * Licensed to the Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9472#issuecomment-154509201
Build triggered. sha1 is merged.
---
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/9472#issuecomment-154509236
Build started sha1 is merged.
---
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/9472#issuecomment-154509884
**[Test build #45238 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45238/consoleFull)**
for PR 9472 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9480#discussion_r44177613
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/EquivalentExpressions.scala
---
@@ -0,0 +1,108 @@
+/*
+ * Licensed to
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9480#discussion_r44178151
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -341,7 +440,18 @@ abstract class
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/9524#issuecomment-154510939
@rxin Ok I'll update this to use Janino although I'll miss my compile time
type checking I figured I'd probably have to do that. In the meantime does the
API look like
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9504#issuecomment-154511541
Build triggered. sha1 is merged.
---
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/9504#issuecomment-154511574
Build started sha1 is merged.
---
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 nilmeier commented on the pull request:
https://github.com/apache/spark/pull/8563#issuecomment-154499019
Thank you for the comments Yu. I'll update these in the next few days.
Best, Jerome
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-154499514
**[Test build #45232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45232/consoleFull)**
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9409#issuecomment-154499913
Build triggered. sha1 is merged.
---
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/9517#issuecomment-154499940
Build started sha1 is merged.
---
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/9409#issuecomment-154499941
Build started sha1 is merged.
---
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/9517#issuecomment-154499906
Build triggered. sha1 is merged.
---
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9143#discussion_r44174052
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/util/BatchedWriteAheadLog.scala
---
@@ -0,0 +1,206 @@
+/*
+ * Licensed to the Apache
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/6291#issuecomment-154502060
Nothing actually new -- I still think this one is ready to go after a
little review. I am noting, however, that the prior discussion misses one
element that raises
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9143#discussion_r44174435
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/util/BatchedWriteAheadLog.scala
---
@@ -0,0 +1,206 @@
+/*
+ * Licensed to the Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9517#issuecomment-154502199
Build started sha1 is merged.
---
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/9517#issuecomment-154502163
Build triggered. sha1 is merged.
---
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 rekhajoshm opened a pull request:
https://github.com/apache/spark/pull/9525
[SPARK-11531] [ML] : SparseVector error Msg
PySpark SparseVector should have "Found duplicate indices" error message
You can merge this pull request into a Git repository by running:
$ git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9525#issuecomment-154503752
Build triggered. sha1 is merged.
---
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/9517#issuecomment-154503748
Build finished. No test results found.
---
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/9517#issuecomment-154503753
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45233/
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9525#issuecomment-154504166
**[Test build #45236 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45236/consoleFull)**
for PR 9525 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9468
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9453#issuecomment-154504554
Thanks for reviewing! I am merging it 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
301 - 400 of 727 matches
Mail list logo
