Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16387
**[Test build #71068 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71068/testReport)**
for PR 16387 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16511
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16511
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71066/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16511
**[Test build #71066 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71066/testReport)**
for PR 16511 at commit
Github user leonfl commented on the issue:
https://github.com/apache/spark/pull/16486
@jkbradley, Could you also help to check this patch cause you are familiar
with this defect, Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16513
**[Test build #71067 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71067/testReport)**
for PR 16513 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16513
@JoshRosen
---
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
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/16513
[SPARK-12757][CORE] lower "block locks were not released" log to info level
## What changes were proposed in this pull request?
lower "block locks were not released" log to info level
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71064/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #71064 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71064/testReport)**
for PR 15671 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16511
**[Test build #71066 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71066/testReport)**
for PR 16511 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16511
turns out Gamma is broken. will be working on adding tests
---
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 issue:
https://github.com/apache/spark/pull/16432
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71065/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16432
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16432
**[Test build #71065 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71065/testReport)**
for PR 16432 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15539
It could return incorrect results, but I need to prove it using a use case.
We always call
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16510
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71062/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16510
**[Test build #71062 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71062/testReport)**
for PR 16510 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16510
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15539
Hm, what use cases are we trying to address? As I understand, the worst
that can happen if the cache size flag is toggled at runtime is that the old
settings might still apply. And when the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16512
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71061/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16512
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16512
**[Test build #71061 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71061/testReport)**
for PR 16512 at commit
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/16497
@tanejagagan Would you please revert the unnecessary code changes?
BTW: You can test the scala style on local environment by running
`./dev/lint-scala` from console.
---
If your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16501
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71058/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16501
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16501
**[Test build #71058 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71058/testReport)**
for PR 16501 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16432
**[Test build #71065 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71065/testReport)**
for PR 16432 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16511
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16511
**[Test build #71060 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71060/testReport)**
for PR 16511 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16511
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71060/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16474
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71055/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16474
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16474
**[Test build #71055 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71055/testReport)**
for PR 16474 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16233
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16233
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71057/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #71064 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71064/testReport)**
for PR 15671 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16474
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16233
**[Test build #71057 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71057/testReport)**
for PR 16233 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16474
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71053/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16474
**[Test build #71053 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71053/testReport)**
for PR 16474 at commit
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/16401
OK I'll submit a pr to fix 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 this feature
enabled and
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16401
hm concrete suggestion:
1. pass the conf and cache the computed statistics the first time
2. have a simple invalidateStatsCache method that can be called manually to
invalidate.
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/16401
So you mean we still pass the conf and do caching, and also add the
invalidation method, although the cache invalidation logic has some problem in
current stage?
---
If your project is set up for
Github user xiaochang-wu commented on the issue:
https://github.com/apache/spark/pull/16411
@tgravescs Thanks for your comments. There are two things we have tried.
1) To add a prefix command on executor launch
I agree this opens a door for user to do anything for
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/16395
@ron8hu Can you update the test cases based on the latest master? We have a
new test infrastructure now.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/12414
hi - where are we on this?
@yanboliang could you add `[SPARKR]` to the title
---
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 issue:
https://github.com/apache/spark/pull/16510
**[Test build #71062 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71062/testReport)**
for PR 16510 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15480
**[Test build #71063 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71063/testReport)**
for PR 15480 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16512
**[Test build #71061 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71061/testReport)**
for PR 16512 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16401
But you can't do a lazy val unless you have the conf passed in, since you
will be adding knobs to the CBO stats soon wouldn't you?
Also there is really nothing basic vs CBO here. Both are
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/16432#discussion_r95104135
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/security/HadoopFSCredentialProvider.scala
---
@@ -56,14 +57,14 @@
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/16512
[SPARK-18335][SPARKR] createDataFrame to support numPartitions parameter
## What changes were proposed in this pull request?
To allow specifying number of partitions when the DataFrame
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/16432#discussion_r95104079
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/security/HadoopFSCredentialProvider.scala
---
@@ -56,14 +57,14 @@
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16511
**[Test build #71060 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71060/testReport)**
for PR 16511 at commit
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16511#discussion_r95103899
--- Diff: R/pkg/R/mllib_regression.R ---
@@ -52,6 +52,8 @@ setClass("IsotonicRegressionModel", representation(jobj =
"jobj"))
#' This
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16511
@yanboliang
---
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
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/16511
[SPARKR][DOCS] clarify glm family supported
## What changes were proposed in this pull request?
R family is a longer list than what Spark supports.
## How was this patch
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16432#discussion_r95103785
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/security/HadoopFSCredentialProvider.scala
---
@@ -56,14 +57,14 @@
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/16431
OK, I'll update this pr today.
---
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
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/16401
If our goal is to fix two sets of stats issue first, is it ok to just use
two `lazy val`s now, and leave the configuration and cache invalidation issues
in the future? In current implementation, we
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16432#discussion_r95103643
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/security/HadoopFSCredentialProvider.scala
---
@@ -56,14 +57,14 @@
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16431#discussion_r95103316
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/estimation/AggregateEstimation.scala
---
@@ -0,0 +1,59 @@
+/*
+ *
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16431
Can you update the pull request and the test cases to use the new test
infra?
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/16430
---
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 issue:
https://github.com/apache/spark/pull/16510
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16510
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71059/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16510
**[Test build #71059 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71059/testReport)**
for PR 16510 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16430
Alright I'm going to merge this since this patch introduces test
infrastructure that can be used by other tests. Please submit a follow-up PR to
add more test cases.
---
If your project is set
Github user gczsjdy commented on a diff in the pull request:
https://github.com/apache/spark/pull/16476#discussion_r95102912
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -340,3 +341,91 @@ object CaseKeyWhen {
Github user gczsjdy commented on a diff in the pull request:
https://github.com/apache/spark/pull/16476#discussion_r95102842
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -340,3 +341,91 @@ object CaseKeyWhen {
Github user felixcheung closed the pull request at:
https://github.com/apache/spark/pull/16507
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16507
merged to branch-2.1
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16504
---
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/16504
merged to master & branch-2.1
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16504
@anabranch the failure is not from Jenkins but from (R only) AppVeyor
tests. It looks like it is nothing related - it failed at access github.
---
If your project is set up for it, you can
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16510
**[Test build #71059 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71059/testReport)**
for PR 16510 at commit
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/16510
[SPARK-19130][SPARKR] Support setting literal value as column implicitly
## What changes were proposed in this pull request?
```
df$foo <- 1
```
instead of
```
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16432
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71056/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16432
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16432
**[Test build #71056 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71056/testReport)**
for PR 16432 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16432
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71054/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16432
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16501
Build started: [TESTS] `org.apache.spark.sql.hive.execution.HiveQuerySuite`
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16432
**[Test build #71054 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71054/testReport)**
for PR 16432 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16501
**[Test build #71058 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71058/testReport)**
for PR 16501 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15539
Yeah, I think we should document the behavior issues when different
sessions are using different conf values. Will do it. I think we also need to
evict all the cache that are associated with the
Github user hustfxj commented on the issue:
https://github.com/apache/spark/pull/16443
@srowen I can't fix the description at this PR, so I close the PR and
recreate the new PR for this bug. You can review it at
https://github.com/apache/spark/pull/16509.
---
If your project is
Github user hustfxj closed the pull request at:
https://github.com/apache/spark/pull/16443
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15539
`(ClientId, Path), Array[FileStatus]` uh... `FileStatusCache` does not
share any entries with any other client, but does share memory resources for
the purpose of cache eviction.
Sorry,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16509
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 project does not have this
GitHub user hustfxj opened a pull request:
https://github.com/apache/spark/pull/16509
[SPARK-19042] spark executor can't download the jars when uber jar's http
url contaâ¦
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16233
**[Test build #71057 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71057/testReport)**
for PR 16233 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16474
**[Test build #71055 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71055/testReport)**
for PR 16474 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16432
**[Test build #71056 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71056/testReport)**
for PR 16432 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16508
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 project does not have this
GitHub user liujianhuiouc opened a pull request:
https://github.com/apache/spark/pull/16508
[spark-18806] [core] the processors DriverWrapper and
CoarseGrainedExecutorBackend should be exit when worker exit
## What changes were proposed in this pull request?
modify the
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/16432
@tgravescs thanks for your comments, I also tested with webhdfs with
configuration like:
```
--conf spark.yarn.access.namenodes=webhdfs://c6402.ambari.apache.org:50070/
```
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16474
**[Test build #71053 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71053/testReport)**
for PR 16474 at commit
1 - 100 of 277 matches
Mail list logo
