Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/9902#discussion_r45689018
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/literals.scala
---
@@ -32,6 +32,7 @@ object Literal {
case
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-159132863
**[Test build #46576 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46576/consoleFull)**
for PR 7753 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9457#issuecomment-159134146
**[Test build #46574 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46574/consoleFull)**
for PR 9457 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9917#issuecomment-159134283
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/9917#issuecomment-159134285
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user ashwinswaroop opened a pull request:
https://github.com/apache/spark/pull/9926
SPARK-11686
Changed the log type to a 'warning' instead of 'info' as required.
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9923#issuecomment-159134288
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/9756#issuecomment-159134462
**[Test build #46578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46578/consoleFull)**
for PR 9756 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8714#discussion_r45691536
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -702,8 +712,6 @@ private[deploy] class Master(
Github user hhbyyh commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-159136664
@jkbradley Thanks for review.
Do you mean a LDAModel.load(path) which can load both local and distributed
LDAModel? We can create a jira.
---
If your project
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8714#discussion_r45692237
--- Diff:
core/src/main/scala/org/apache/spark/deploy/client/AppClient.scala ---
@@ -178,9 +178,6 @@ private[spark] class AppClient(
val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-159137662
**[Test build #46581 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46581/consoleFull)**
for PR 9894 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9919#issuecomment-159138835
**[Test build #46560 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46560/consoleFull)**
for PR 9919 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9793#discussion_r45693587
--- Diff:
core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeExternalSorter.java
---
@@ -489,10 +495,6 @@ public void loadNext() throws
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9919#issuecomment-159140321
**[Test build #2099 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2099/consoleFull)**
for PR 9919 at commit
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/4887#issuecomment-159140817
@andrewor14 I have the impression that cogroup will hold tow RDD's
iterator,
If the first iterator is `MEMORY_ONLY`, and unroll failed, so the iterator
is based
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9918#issuecomment-159141995
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9377
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/9377#issuecomment-159143174
Thanks - going to merge 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 project does not have
Github user Lewuathe commented on the pull request:
https://github.com/apache/spark/pull/9756#issuecomment-159125433
@nakul02 Thank you so much for quick updating!
---
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 jodersky opened a pull request:
https://github.com/apache/spark/pull/9925
[SPARK-7286] [SQL] Deprecate !== in favour of =!=
Fixes subtle issues related to operator precedence, as discussed in
SPARK-7286.
I'm not entirely sure this is the right thing to do,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9918#issuecomment-159127225
**[Test build #46575 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46575/consoleFull)**
for PR 9918 at commit
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/9902#discussion_r45689230
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -343,47 +343,71 @@ case class
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/9925#discussion_r45690182
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/dsl/package.scala ---
@@ -83,7 +83,10 @@ package object dsl {
def >= (other:
Github user nakul02 commented on the pull request:
https://github.com/apache/spark/pull/9756#issuecomment-159133997
@Lewuathe - sorry, it took a while to regenerate numbers for all the tests
---
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/9457#issuecomment-159134236
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/9923#issuecomment-159134286
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/9457#issuecomment-159134237
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/9923#issuecomment-159134192
**[Test build #46566 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46566/consoleFull)**
for PR 9923 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9917#issuecomment-159134234
**[Test build #46557 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46557/consoleFull)**
for PR 9917 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9840#issuecomment-159134874
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/9924#issuecomment-159134861
**[Test build #46579 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46579/consoleFull)**
for PR 9924 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9926#issuecomment-159134679
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/9840#issuecomment-159134875
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/9844#issuecomment-159136027
**[Test build #46580 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46580/consoleFull)**
for PR 9844 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8714#discussion_r45692382
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -702,8 +712,6 @@ private[deploy] class Master(
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9917#issuecomment-159137841
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-159137863
@jerryshao this change looks pretty good. I think I have a good
understanding of the problem. The behavior before this patch was:
1. Master launches an
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-159139182
**[Test build #46580 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46580/consoleFull)**
for PR 9844 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-159139215
Test FAILed.
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/9844#issuecomment-159139214
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/9756#issuecomment-159139789
**[Test build #46578 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46578/consoleFull)**
for PR 9756 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9756#issuecomment-159139868
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/9918#issuecomment-159141994
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 sun-rui commented on the pull request:
https://github.com/apache/spark/pull/9835#issuecomment-159141992
I realize that this takes more effort than I expected as we'd better
support specifying columns without $ for all DataFrame methods that take any
argument of "Column"
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9918#issuecomment-159141891
**[Test build #46575 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46575/consoleFull)**
for PR 9918 at commit
Github user saurfang commented on the pull request:
https://github.com/apache/spark/pull/8375#issuecomment-159143064
I myself definitely want to get this merged. That being said, this will
require a spark committer to drive the process. If you feel strongly about this
feature, voice
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9928
[SPARK-11942][SQL] fix encoder life cycle for CoGroup
we should pass in resolved encodera to logical `CoGroup` and bind them in
physical `CoGroup`
You can merge this pull request into a Git
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9840#issuecomment-159181742
It's blocked by https://github.com/apache/spark/pull/9928
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9918#discussion_r45703494
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -689,6 +689,7 @@ object functions extends LegacyFunctions {
* @group
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9928#issuecomment-159182159
**[Test build #46586 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46586/consoleFull)**
for PR 9928 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-159186937
**[Test build #46588 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46588/consoleFull)**
for PR 9844 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-159187032
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-159187716
The following two tests have failed for the past three builds in the Hadoop
2.4 Maven Jenkins job:
- org.apache.spark.deploy.yarn.YarnClusterSuite.run Spark
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-159188789
@cloud-fan can you please help trigger a retest ? Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9860#issuecomment-159182921
I worry that this opens a can of UI / UX worms for very little net benefit
to users. For instance, a common complaint with the Jenkins auto-refresh is
that the delay
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9860#issuecomment-159183472
I can add a text field to let users configure the refresh interval if you
want.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-159187034
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9844#issuecomment-159188818
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/9837#issuecomment-158965258
I made comments on https://github.com/apache/spark/pull/9859.
---
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/6935#issuecomment-158971340
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/6935#issuecomment-158971329
**[Test build #46537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46537/consoleFull)**
for PR 6935 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-158971335
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/6935#issuecomment-158957678
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/6935#issuecomment-158957671
**[Test build #46535 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46535/consoleFull)**
for PR 6935 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9910#issuecomment-158957920
I tend to agree with that, if in fact this is a warning only, and somewhat
commonly encountered in normal operation during shutdown. This code path
doesn't only occur
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9910#issuecomment-158963382
It's the cause of the warning that I see during shutdown (and not randomly,
I always have the exception).
---
If your project is set up for it, you can reply to this
Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/6545#issuecomment-158969374
...I'm looking at this and my PR; I think they are differently
interdependent.
1. This patch adds a new method to `ApplicationHistoryProvider` for the
Github user ted-yu commented on the pull request:
https://github.com/apache/spark/pull/9862#issuecomment-158959620
@marmbrus
Is there anything I need to do ?
---
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 steveloughran commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-158971646
As discussed on #6545, I think we could actually switch to live UI
playback, provided the number of cached UIs was kept down.
What must be done here is
Github user mariusvniekerk commented on a diff in the pull request:
https://github.com/apache/spark/pull/9861#discussion_r45620973
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JDBCRDD.scala
---
@@ -489,6 +492,13 @@ private[sql] class JDBCRDD(
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/9875#issuecomment-158958240
@harishreedharan I thought this issue existed even without reusing the jvm
(going by other jira and prs that were filed)? For instance if you just have a
long
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-158964110
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-158964006
**[Test build #46533 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46533/consoleFull)**
for PR 7753 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9861#issuecomment-158984200
**[Test build #46538 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46538/consoleFull)**
for PR 9861 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-158970671
**[Test build #46537 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46537/consoleFull)**
for PR 6935 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9861#discussion_r45622542
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JDBCRDD.scala
---
@@ -489,6 +492,13 @@ private[sql] class JDBCRDD(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-158994786
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/8610#issuecomment-158994687
**[Test build #46536 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46536/consoleFull)**
for PR 8610 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9747
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-159025832
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-159027545
**[Test build #46542 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46542/consoleFull)**
for PR 9530 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9912#issuecomment-159027567
**[Test build #46540 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46540/consoleFull)**
for PR 9912 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9912#issuecomment-159027731
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/9912#issuecomment-159027730
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 steveloughran opened a pull request:
https://github.com/apache/spark/pull/9913
[SPARK-7889] [Core] WiP History Caching: xu tingjun's patch against master
This is @XuTingjun's patch (#6545) reapplied to trunk with a bit of cleanup
(the probe in the history provider is
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/9911
[WIP][SPARK-9686][SQL] Redirect JDBC metadata calls to Spark SQL metadata
Hive client
This PR is based on the patch @navis provided in [SPARK-9686][1].
Basically, it overrides all JDBC
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9911#issuecomment-158990791
**[Test build #46539 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46539/consoleFull)**
for PR 9911 at commit
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/9875#issuecomment-158988545
Yes, that is correct but this happens even without the tokens expiring.
What do you think about doing the relogin in the
YarnCLientSchedulerBackend?
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-158995626
Jenkins, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9911#issuecomment-159011485
**[Test build #46539 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46539/consoleFull)**
for PR 9911 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9911#issuecomment-159011554
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/9911#issuecomment-159011557
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159011450
Since `ctx.close()` is asynchronous, this one doesn't fix the race totally.
Right?
---
If your project is set up for it, you can reply to this email and have your
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159003767
/cc @rxin @zsxwing ; we should probably get this into 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.
Github user woj-i commented on the pull request:
https://github.com/apache/spark/pull/9859#issuecomment-159010452
Hi!
Can you test it on all environments? If not, then I can shrink the scope to
the YARN and the local mode.
In case of HADOOP_SECURITY_AUTHENTICATION there
GitHub user sethah opened a pull request:
https://github.com/apache/spark/pull/9912
[SPARK-11861][ML] Add feature importances for decision trees
This patch adds an API entry point for single decision tree feature
importances.
You can merge this pull request into a Git repository
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-158964111
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/8610#issuecomment-158969995
**[Test build #46536 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46536/consoleFull)**
for PR 8610 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9612#issuecomment-158993697
Thanks! 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
401 - 500 of 556 matches
Mail list logo
