Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14452
**[Test build #63108 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63108/consoleFull)**
for PR 14452 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14452
**[Test build #63107 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63107/consoleFull)**
for PR 14452 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/14452
[SPARK-16849][SQL] Improve subquery execution by deduplicating the
subqueries with the same results
## What changes were proposed in this pull request?
The subqueries in SparkSQL will be
Github user zzcclp commented on the issue:
https://github.com/apache/spark/pull/14420
@JoshRosen can you have a look at this pr?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14451
Yeah, keep it open. That PR just tries to get all the possible holes
(corner cases). You know, I do not care which PR is merged, but, in my
opinion, we need to cover all the cases. That is for
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14451
Oh, you took a look already. Yes, it seems your PR includes this change. Do
you mind if I leave this open? This bit seems arguably get merged quickly.
I don't mind if this credits to
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14451
Is this related to: https://github.com/apache/spark/pull/13770?
---
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 issue:
https://github.com/apache/spark/pull/14451
**[Test build #63106 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63106/consoleFull)**
for PR 14451 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/14451
Make jdbc() and read.format("jdbc") consistently throwing exception for
user-specified schema
## What changes were proposed in this pull request?
Currently,
```scala
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14449
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14298
**[Test build #63105 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63105/consoleFull)**
for PR 14298 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14450
This will be a legitimate change because this replaces the deprecated usage
of constructor. Please let me cc @liancheng and @srowen as well as it is also
partly about building.
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14450
**[Test build #63104 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63104/consoleFull)**
for PR 14450 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/14450
[SPARK-16847][SQL] Prevent to potentially read corrupt statstics on binary
in Parquet a VectorizedReader
## What changes were proposed in this pull request?
it is still possible to
GitHub user mpjlu opened a pull request:
https://github.com/apache/spark/pull/14449
[SPARK-16843][MLLIB] add the percentage ChiSquareSelector feature
## What changes were proposed in this pull request?
add the percentage ChiSquareSelector feature
## How was
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14446
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63101/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14446
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/14446
**[Test build #63101 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63101/consoleFull)**
for PR 14446 at commit
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/11411
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 feature
enabled and wishes
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/12135
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 feature
enabled and wishes
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/12983
@srowen In Python2, `xrange` is more efficient than `range`.
This PR add 'range = xrange' in files like `python/pyspark/accumulators.py`
`python/pyspark/heapq3.py`
Github user zhengruifeng closed the pull request at:
https://github.com/apache/spark/pull/13657
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14368
**[Test build #63103 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63103/consoleFull)**
for PR 14368 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14368
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/14368
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63103/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14448
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/14448
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63102/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14448
**[Test build #63102 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63102/consoleFull)**
for PR 14448 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14368
**[Test build #63103 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63103/consoleFull)**
for PR 14368 at commit
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/13893
ping @cloud-fan
---
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
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14368
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 feature
enabled and wishes
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14368
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/14401
@rxin As @yhuai previously addressed, this change benifits in following
cases:
1. Right now, we set the warehouse path to the default one firstly, and
then we override the setting in
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14427
Done
---
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
Github user ericl closed the pull request at:
https://github.com/apache/spark/pull/14427
---
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 issue:
https://github.com/apache/spark/pull/14427
@ericl can you close 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/14427
Merging in branch-2.0.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14448
**[Test build #63102 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63102/consoleFull)**
for PR 14448 at commit
GitHub user junyangq opened a pull request:
https://github.com/apache/spark/pull/14448
[Spark-16579][SparkR] Add install.spark function
## What changes were proposed in this pull request?
Add an `install.spark` function to the SparkR package. User can run
`install.spark()`
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14446
**[Test build #63101 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63101/consoleFull)**
for PR 14446 at commit
Github user clockfly commented on the issue:
https://github.com/apache/spark/pull/14446
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 feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11157
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63099/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11157
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/11157
**[Test build #63099 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63099/consoleFull)**
for PR 11157 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14446
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/14446
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63097/
Test FAILed.
---
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/14440
sounds reasonable...
---
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 JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14396
@zsxwing, I meant to describe what happens on executors in the following
scenario:
- `addFile(foo)` is called for the first time at `timestamp = 1`
- A task runs on an executor and
Github user WeichenXu123 closed the pull request at:
https://github.com/apache/spark/pull/14440
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14446
**[Test build #63097 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63097/consoleFull)**
for PR 14446 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13778
ping @cloud-fan again, this is waiting for a while. Do you have time to
look at again? Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user keypointt commented on the issue:
https://github.com/apache/spark/pull/14447
hi @mengxr , could you please tell me how to debug R wrapper? Thanks a lot
I tried to read documentation and google, but cannot figure it out myself.
From SparkR console, the error
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14442
Can you add an end-to-end test for this in SQLQuerySuite? It's not a great
place but we will refactor it soon.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14447
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14447
**[Test build #63100 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63100/consoleFull)**
for PR 14447 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14447
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63100/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14447
**[Test build #63100 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63100/consoleFull)**
for PR 14447 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14434
---
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 keypointt opened a pull request:
https://github.com/apache/spark/pull/14447
[SPARK-16445][MLlib][SparkR] Multilayer Perceptron Classifier wrapper in
SparkR
https://issues.apache.org/jira/browse/SPARK-16445
## What changes were proposed in this pull request?
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14434
Thanks. Merging to master.
---
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 shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/14392#discussion_r73079016
--- Diff: R/pkg/R/mllib.R ---
@@ -632,3 +659,106 @@ setMethod("predict", signature(object =
"AFTSurvivalRegressionModel"),
function(object,
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/13647
ping @mengxr @jkbradley @yanboliang Can you give me some comments on this
PR? I can start improving it for 2.1+.
Thanks!
---
If your project is set up for it, you can reply to this
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/14433
@felixcheung I will try to retrieve terminal/shell type before printing out
the message. I will update the PR if I can find a way of doing that. Thanks!
---
If your project is set up for it,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14445
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63096/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14445
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/14445
**[Test build #63096 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63096/consoleFull)**
for PR 14445 at commit
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/14368#discussion_r73076628
--- Diff: examples/src/main/r/RSparkSQLExample.R ---
@@ -18,31 +18,43 @@
library(SparkR)
# $example on:init_session$
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11157
**[Test build #63099 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63099/consoleFull)**
for PR 11157 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11157
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/11157
**[Test build #63098 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63098/consoleFull)**
for PR 11157 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11157
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63098/
Test FAILed.
---
Github user skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/11157#discussion_r73074211
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala
---
@@ -356,4 +374,233 @@ private[mesos] trait
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11157
**[Test build #63098 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63098/consoleFull)**
for PR 11157 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14446
**[Test build #63097 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63097/consoleFull)**
for PR 14446 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14434#discussion_r73073652
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -662,10 +662,6 @@ object NullPropagation extends
GitHub user clockfly opened a pull request:
https://github.com/apache/spark/pull/14446
[SPARK-16841][SQL] Improves the row level metrics performance when reading
Parquet table
## What changes were proposed in this pull request?
When reading from Parquet table, Spark
Github user nsyca commented on the issue:
https://github.com/apache/spark/pull/14411
@hvanhovell,
First, my apologies for delaying the replies. I am travelling this week,
only getting spontaneous connections. Thank you for your explanation of the
implementation and the
Github user clockfly commented on the issue:
https://github.com/apache/spark/pull/14445
@gatorsmile Thanks! updated.
---
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 sameeragarwal commented on a diff in the pull request:
https://github.com/apache/spark/pull/14176#discussion_r73070005
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/HashAggregateExec.scala
---
@@ -279,9 +280,15 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14384
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63095/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14384
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14445
Maybe, we can correct the PR description and make it more accurate.
This PR avoids the extra memory copy when the vectorized parquet record
reader is not being used for reading a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14384
**[Test build #63095 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63095/consoleFull)**
for PR 14384 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14445
**[Test build #63096 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63096/consoleFull)**
for PR 14445 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14442
LGTM
FYI, MySQL and PostgreSQL support NOW as a synonym of CURRENT_TIMESTAMP
---
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 issue:
https://github.com/apache/spark/pull/14384
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14384
**[Test build #63094 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63094/consoleFull)**
for PR 14384 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14384
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63094/
Test FAILed.
---
GitHub user clockfly opened a pull request:
https://github.com/apache/spark/pull/14445
[SPARK-16320][SQL] Fix performance regression for parquet table with nested
fields
## What changes were proposed in this pull request?
For non-partitioned parquet table with nested
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14439#discussion_r73064350
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/TypeCoercion.scala
---
@@ -157,6 +145,26 @@ object TypeCoercion {
})
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14439
It will be good to summarize the behaviors of other systems in the
description. Let's also explain the behavioral change of this pr in the
description. So, others can understand its implication.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14384
**[Test build #63095 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63095/consoleFull)**
for PR 14384 at commit
Github user yinxusen commented on the issue:
https://github.com/apache/spark/pull/14212
@MLnick They serve different purpose. This one is for users who have built
their tools upon it. The `LatentDirichletAllocationExample` is for ML docs.
---
If your project is set up for it, you
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/1
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 eyalfa commented on the issue:
https://github.com/apache/spark/pull/1
@cloud-fan
---
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
GitHub user eyalfa opened a pull request:
https://github.com/apache/spark/pull/1
[SPARK-16839] [SQL] redundant aliases after cleanupAliases
## What changes were proposed in this pull request?
a failing test, soon to add a proposed fix
## How was this patch tested?
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14384
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/14384
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63093/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14384
**[Test build #63093 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63093/consoleFull)**
for PR 14384 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14441
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63090/
Test PASSed.
---
1 - 100 of 354 matches
Mail list logo
