Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16467
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16467
LGTM - merging to master/2.1. Thanks!
Sorry for the long wait.
---
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 hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16467#discussion_r97667507
--- Diff:
sql/core/src/test/resources/sql-tests/results/subquery/in-subquery/not-in-multiple-columns.sql.out
---
@@ -0,0 +1,59 @@
+-- Automatically
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16650
**[Test build #71947 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71947/testReport)**
for PR 16650 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16650
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/16650
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71947/
Test FAILed.
---
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/16465
Small follow up ping for @joshrosen to @davies maybe?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16694
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71948/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16694
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/16694
**[Test build #71948 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71948/testReport)**
for PR 16694 at commit
Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/16688
ok to test
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16660
LGTM except one comment. Thanks for working on 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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16660
The remaining comment is:
https://github.com/apache/spark/pull/16660#discussion_r97427591
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15768
**[Test build #3550 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3550/consoleFull)**
for PR 15768 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16650
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/16650
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71944/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16650
**[Test build #71944 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71944/testReport)**
for PR 16650 at commit
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/16329
Sorry for the delay. This LGTM, but I'm currently away from my Apache SSH
keys. Other committers should feel free to merge if you get there before I do.
---
If your project is set up for it,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16694
**[Test build #71948 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71948/testReport)**
for PR 16694 at commit
Github user xwu0226 commented on the issue:
https://github.com/apache/spark/pull/16685
A few comments:
1. The mayor concern is that this solution need to pull in the whole target
table data and do a join operation between the source dataframe and the target
table to
Github user ilganeli commented on the issue:
https://github.com/apache/spark/pull/16685
It sounds like you consider there to be too many errata and assumptions
made in this patch for it to be a worthwhile code contribution. Given the
numerous assumptions made in this PR, how would
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16650
**[Test build #71947 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71947/testReport)**
for PR 16650 at commit
Github user ilganeli commented on the issue:
https://github.com/apache/spark/pull/16685
@gatorsmile That makes a lot of sense. Here is a code snippet that relies
on the database to do the UPSERT:
```
/**
* Generate the SQL statement to perform an upsert (UPDATE
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16694
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/16694
**[Test build #71946 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71946/testReport)**
for PR 16694 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16694
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71946/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16694
**[Test build #71946 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71946/testReport)**
for PR 16694 at commit
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/14702
jenkins retest please
test failure from build HiveSparkSubmitSuite `set
hive.metastore.warehouse.dir` is unrelated to the change
---
If your project is set up for it, you can reply to
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16685
Currently, I do not have a solution for supporting the parallel mass
UPDATE, because the rows in the DataFrame might be out of order and a global
transaction is missing. The solution posted in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16694
**[Test build #71945 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71945/testReport)**
for PR 16694 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16694
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71945/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16694
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/16694
**[Test build #71945 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71945/testReport)**
for PR 16694 at commit
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/16694
cc @hhbyyh 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 not have this feature
enabled and wishes
GitHub user wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/16694
[SPARK-19336][ML][Pyspark]: LinearSVC Python API
## What changes were proposed in this pull request?
Add Python API for the newly added LinearSVC algorithm.
## How was this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16650
**[Test build #71944 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71944/testReport)**
for PR 16650 at commit
Github user jsoltren commented on the issue:
https://github.com/apache/spark/pull/16650
Working through some test failures in
org.apache.spark.deploy.StandaloneDynamicAllocationSuite and
org.apache.spark.HeartbeatReceiverSuite...
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16605
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71940/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16605
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/16605
**[Test build #71940 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71940/testReport)**
for PR 16605 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16686
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/16686
**[Test build #71942 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71942/testReport)**
for PR 16686 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16686
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71942/
Test PASSed.
---
Github user ilganeli commented on the issue:
https://github.com/apache/spark/pull/16685
I recognize that this is not an optimal solution, but Spark has
historically contained multiple sub-optimal operations that are nonetheless
useful in certain contexts and it's left to the user to
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16685
To support the UPSERT, this PR basically implements it by using SELECT,
UPDATE and INSERT. It has to read the whole table from the JDBC-connected
database, and process it in Spark. It does not
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16685
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71943/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16685
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/16685
**[Test build #71943 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71943/testReport)**
for PR 16685 at commit
Github user jsoltren commented on a diff in the pull request:
https://github.com/apache/spark/pull/16650#discussion_r97625393
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistTracker.scala ---
@@ -168,6 +169,21 @@ private[scheduler] class BlacklistTracker (
Github user ilganeli commented on the issue:
https://github.com/apache/spark/pull/16685
@gatorsmile What is a "key" update and in what context would that sort of
operation be needed?
I don't think a secondary index on the table prevent this method from
working, the primary
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16685
**[Test build #71943 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71943/testReport)**
for PR 16685 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16685
I still have a concern for Update, even if we do an update based on key
values. Using this way for update statements, we are still facing
non-deterministic results. For example, you are unable
Github user ilganeli commented on a diff in the pull request:
https://github.com/apache/spark/pull/16685#discussion_r97623026
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -722,14 +724,246 @@ object JdbcUtils extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15768
**[Test build #3550 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3550/consoleFull)**
for PR 15768 at commit
Github user jsoltren commented on a diff in the pull request:
https://github.com/apache/spark/pull/16650#discussion_r97622417
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -719,7 +719,11 @@ private[spark] object TaskSchedulerImpl {
Github user jsoltren commented on a diff in the pull request:
https://github.com/apache/spark/pull/16650#discussion_r97622210
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/TaskSetManagerSuite.scala ---
@@ -429,7 +429,7 @@ class TaskSetManagerSuite extends SparkFunSuite
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16685#discussion_r97622295
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -722,14 +724,246 @@ object JdbcUtils extends
Github user jsoltren commented on a diff in the pull request:
https://github.com/apache/spark/pull/16650#discussion_r97622188
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/BlacklistTrackerSuite.scala ---
@@ -43,7 +43,7 @@ class BlacklistTrackerSuite extends
Github user tcondie commented on a diff in the pull request:
https://github.com/apache/spark/pull/16686#discussion_r97620911
--- Diff:
external/kafka-0-10-sql/src/main/resources/META-INF/services/org.apache.spark.sql.sources.DataSourceRegister
---
@@ -1 +1 @@
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16686
**[Test build #71942 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71942/testReport)**
for PR 16686 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16521
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/16685#discussion_r97619926
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -722,14 +724,246 @@ object JdbcUtils extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14702
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71941/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14702
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/16521
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14702
**[Test build #71941 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71941/testReport)**
for PR 14702 at commit
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/16377
Thanks @jkbradley!
---
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,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16690
**[Test build #71938 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71938/testReport)**
for PR 16690 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16377
---
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/16690
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/16690
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71938/
Test FAILed.
---
Github user tcondie commented on the issue:
https://github.com/apache/spark/pull/16686
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 so,
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16377
LGTM
Thanks!
Merging with 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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15880
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/15880
---
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/16605
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/16605
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71939/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16605
**[Test build #71939 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71939/testReport)**
for PR 16605 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16355
Oh OK! Thanks @srowen
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16677
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71936/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16677
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/16677
**[Test build #71936 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71936/testReport)**
for PR 16677 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16582
> Why not simply remove old redirect handler like collection.removeHandler ?
I find it cleaner to just not do something that to do it then have to undo
things when they fail.
---
If your
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16582#discussion_r97610826
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -274,25 +277,28 @@ private[spark] object JettyUtils extends Logging {
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16582#discussion_r97610759
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -337,17 +350,20 @@ private[spark] object JettyUtils extends Logging {
Github user paragpc commented on the issue:
https://github.com/apache/spark/pull/11867
thanks @squito :)
---
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,
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16689
yes. but please see my other comment
---
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/16661
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71937/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16661
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/16661
**[Test build #71937 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71937/testReport)**
for PR 16661 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14702
**[Test build #71941 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71941/testReport)**
for PR 14702 at commit
Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/16688
cc @cloud-fan @gatorsmile Could you please trigger a test for this. Not
sure why the last run didn't succeed. Thanks a lot.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16605
**[Test build #71940 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71940/testReport)**
for PR 16605 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16387
No the question is whether you tested without @viirya commit `b1ef9ec` (the
last one that forces spills of in-memory maps), or just the very last version
of the patch.
---
If your project is set
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16605
**[Test build #71939 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71939/testReport)**
for PR 16605 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16329#discussion_r97590536
--- Diff:
examples/src/main/java/org/apache/spark/examples/sql/JavaUserDefinedTypedAggregation.java
---
@@ -0,0 +1,160 @@
+/*
+ * Licensed to the
Github user aokolnychyi commented on a diff in the pull request:
https://github.com/apache/spark/pull/16329#discussion_r97589440
--- Diff:
examples/src/main/java/org/apache/spark/examples/sql/JavaUserDefinedTypedAggregation.java
---
@@ -0,0 +1,160 @@
+/*
+ * Licensed to
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16690
cc @vanzin @zsxwing
(I was going to make a longer comment about removing `askWithRetry` and
whether we need another method, but then saw the comments on the referenced PR
-- I'll defer to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16605
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71935/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16690
**[Test build #71938 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71938/testReport)**
for PR 16690 at commit
201 - 300 of 457 matches
Mail list logo
