Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8916#issuecomment-143138155
[Test build #43012 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43012/consoleFull)
for PR 8916 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8916#issuecomment-143137880
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/8747#issuecomment-143139114
[Test build #43013 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43013/consoleFull)
for PR 8747 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8914#issuecomment-143142439
[Test build #43006 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43006/console)
for PR 8914 at commit
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/5742#issuecomment-143142324
@jkbradley This test error is not caused by the code, pls retest it when
possible. :)
---
If your project is set up for it, you can reply to this email and have your
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/8879#discussion_r40404014
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -531,6 +531,32 @@ class SQLContext(@transient val sparkContext:
SparkContext)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8915#issuecomment-143146792
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/8915#issuecomment-143146765
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/8915#issuecomment-143147574
[Test build #43014 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43014/consoleFull)
for PR 8915 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8911#discussion_r40404934
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkHadoopUtil.scala
---
@@ -385,20 +385,13 @@ class SparkHadoopUtil extends Logging {
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143149940
As long as use of unsafe can still be turned off and is still pretty
'private' inside core, seems like it doesn't change much.
---
If your project is set up for it, you
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8830
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/8830#issuecomment-143150875
LGTM. Merged into master. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8910#discussion_r40406320
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnSparkHadoopUtil.scala ---
@@ -314,5 +314,28 @@ object YarnSparkHadoopUtil {
def
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8910#discussion_r40406280
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnSparkHadoopUtil.scala ---
@@ -314,5 +314,28 @@ object YarnSparkHadoopUtil {
def
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8910#discussion_r40406303
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnSparkHadoopUtil.scala ---
@@ -314,5 +314,28 @@ object YarnSparkHadoopUtil {
def
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143152016
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/8917#issuecomment-143160497
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/8917#issuecomment-143160477
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/8917#issuecomment-143161249
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/8912#issuecomment-143161248
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/8917#issuecomment-143161230
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/8912#issuecomment-143161232
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/8917#issuecomment-143161870
[Test build #43017 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43017/consoleFull)
for PR 8917 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8917#discussion_r40409805
--- Diff: docs/sql-programming-guide.md ---
@@ -1320,6 +1320,39 @@ Configuration of Parquet can be done using the
`setConf` method on `SQLContext`
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8758#issuecomment-143148811
Seems pretty reasonable to me. The only issue is that it will mean existing
invocations of the script no longer work, right? I wonder if it's possible to
parse the first
Github user dibbhatt commented on the pull request:
https://github.com/apache/spark/pull/8817#issuecomment-143151201
hi @andrewor14 @tdas , kindly let me know if this PR makes sense .
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8904#issuecomment-143151203
`Returns`
---
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/8915#issuecomment-143153462
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/8915#issuecomment-143153463
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/8916#issuecomment-143155658
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/8916#issuecomment-143155566
[Test build #43012 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43012/console)
for PR 8916 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8747#issuecomment-143155835
[Test build #43013 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43013/console)
for PR 8747 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8916#issuecomment-143155656
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 chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/8917
[SPARK-10831][SQL]Add more configuration description
spark.sql.planner.sortMergeJoin
spark.sql.codegen
spark.sql.caseSensitive
spark.sql.dialect
You can merge this pull request
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8917#issuecomment-143162873
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/8917#issuecomment-143162871
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/8917#issuecomment-143164252
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/8917#issuecomment-143164253
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8911#discussion_r40404998
--- Diff:
yarn/src/test/scala/org/apache/spark/deploy/yarn/YarnSparkHadoopUtilSuite.scala
---
@@ -233,4 +233,17 @@ class YarnSparkHadoopUtilSuite extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8758#discussion_r40405373
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerArgumentsSuite.scala
---
@@ -0,0 +1,67 @@
+/*
+ * Licensed to the Apache
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8758#discussion_r40405402
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerArgumentsSuite.scala
---
@@ -0,0 +1,67 @@
+/*
+ * Licensed to the Apache
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8758#discussion_r40405360
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServerArguments.scala
---
@@ -61,6 +61,7 @@ private[history] class
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5722#issuecomment-143150572
I'd say it slightly differently: the goal is to define, for every
configurable port, a range of 1 or more port numbers that may be bound to it.
It could be a single
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143151797
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143151781
Created https://issues.apache.org/jira/browse/SPARK-10830.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143151996
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/8323#issuecomment-143152365
[Test build #43015 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43015/consoleFull)
for PR 8323 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8915#issuecomment-143153353
[Test build #43011 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43011/console)
for PR 8915 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8747#issuecomment-143155921
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/8747#issuecomment-143155922
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/8323#issuecomment-143158210
[Test build #43015 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43015/console)
for PR 8323 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-143158438
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/8323#issuecomment-143158439
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143161069
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8917#discussion_r40409790
--- Diff: docs/sql-programming-guide.md ---
@@ -1320,6 +1320,39 @@ Configuration of Parquet can be done using the
`setConf` method on `SQLContext`
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8912#issuecomment-143162410
[Test build #43018 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43018/consoleFull)
for PR 8912 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8917#issuecomment-143164152
[Test build #43017 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43017/console)
for PR 8917 at commit
Github user y-shimizu commented on the pull request:
https://github.com/apache/spark/pull/8904#issuecomment-143164580
@mengxr I fixed.
---
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/8718#issuecomment-143194884
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/8718#issuecomment-143194792
[Test build #43020 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43020/console)
for PR 8718 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-143194885
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/8918#issuecomment-143192978
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/8918#issuecomment-143192975
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/8916#issuecomment-143137888
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/8747#issuecomment-143138322
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 chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/8915#discussion_r40402018
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/IsolatedClientLoader.scala
---
@@ -174,8 +174,6 @@ private[hive] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8747#issuecomment-143138326
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 a diff in the pull request:
https://github.com/apache/spark/pull/8879#discussion_r40403357
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -531,6 +531,32 @@ class SQLContext(@transient val sparkContext:
SparkContext)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8914#issuecomment-143142585
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/8914#issuecomment-143142581
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 the pull request:
https://github.com/apache/spark/pull/8903#issuecomment-143144117
Hi @viirya , can you explain it a bit more how the extra
`outputNeedConversion` flag help us eliminate the extra conversion? I think I
missed something here.
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8884#issuecomment-143185558
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/8884#issuecomment-143185562
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/8884#issuecomment-143185352
[Test build #43021 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43021/console)
for PR 8884 at commit
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/8919
[SPARK-10833] [BUILD] [WIP] Inline, organize BSD/MIT licenses in LICENSE
*Work in progress -- don't merge yet*
In the course of https://issues.apache.org/jira/browse/LEGAL-226 it came to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8919#issuecomment-143226332
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/8919#issuecomment-143226362
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/8919#issuecomment-143228111
[Test build #43023 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43023/consoleFull)
for PR 8919 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8919#issuecomment-143231258
[Test build #43023 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43023/console)
for PR 8919 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8919#issuecomment-143231295
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/8919#issuecomment-143231292
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/8915#issuecomment-143166731
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/8915#issuecomment-143166607
[Test build #43014 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43014/console)
for PR 8915 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8915#issuecomment-143166732
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/8918#issuecomment-143170183
[Test build #43019 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43019/consoleFull)
for PR 8918 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-143175194
[Test build #43020 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43020/consoleFull)
for PR 8718 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8884#issuecomment-143179460
[Test build #43021 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43021/consoleFull)
for PR 8884 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-143180019
[Test build #43022 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43022/consoleFull)
for PR 8718 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-143182663
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/8718#issuecomment-143182633
[Test build #43022 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43022/console)
for PR 8718 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-143182661
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 SaintBacchus opened a pull request:
https://github.com/apache/spark/pull/8918
[SPARK-10766][SPARK-SUBMIT]Add some configuration for the client process in
cluster mode.
Add this four configurations for the client only in cluster mode:
* `spark.client.memory` of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-143170062
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/8918#issuecomment-143170043
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 SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/8867#issuecomment-143173483
@tgravescs I had noticed the code of
`UserGroupInformation.loginUserFromKeytab(args.principal, args.keytab)`
After this login motivation, `yarn.Client` will
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8718#issuecomment-143174139
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/8718#issuecomment-143174116
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/8904#issuecomment-143174303
[Test build #1815 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1815/consoleFull)
for PR 8904 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8904#issuecomment-143174654
[Test build #1815 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1815/console)
for PR 8904 at commit
201 - 300 of 306 matches
Mail list logo
