Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/17172#discussion_r105252628
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/objects.scala ---
@@ -216,10 +217,39 @@ case class MapElementsExec(
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/17172#discussion_r105252486
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetBenchmark.scala ---
@@ -165,11 +208,23 @@ object DatasetBenchmark {
val numRows =
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/16845
So being able to format the messages in the 2.X line and 3 line seems like
a reasonable improvement, even if we are using a deprecated feature in 2.6+ for
the 2.X line. Let me know when you have a
Github user dgingrich commented on a diff in the pull request:
https://github.com/apache/spark/pull/17213#discussion_r105246855
--- Diff: python/pyspark/sql/types.py ---
@@ -1300,70 +1300,71 @@ def _verify_type(obj, dataType, nullable=True):
if nullable:
Github user dgingrich commented on a diff in the pull request:
https://github.com/apache/spark/pull/17213#discussion_r105247143
--- Diff: python/pyspark/sql/types.py ---
@@ -1300,70 +1300,71 @@ def _verify_type(obj, dataType, nullable=True):
if nullable:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15009
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/15009
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74272/
Test PASSed.
---
Github user dgingrich commented on a diff in the pull request:
https://github.com/apache/spark/pull/16845#discussion_r105249885
--- Diff: python/pyspark/util.py ---
@@ -0,0 +1,45 @@
+# -*- coding: utf-8 -*-
+#
+# Licensed to the Apache Software Foundation (ASF) under
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15009
**[Test build #74272 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74272/testReport)**
for PR 15009 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17202
LGTM. Merging to master and 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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17227
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 dgingrich commented on the issue:
https://github.com/apache/spark/pull/17227
Opening as a comparison for https://github.com/apache/spark/pull/17213
---
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 dgingrich opened a pull request:
https://github.com/apache/spark/pull/17227
[SPARK-19507][PySpark][SQL] Show field name in _verify_type error
## What changes were proposed in this pull request?
Add better error messages to _verify_type to track down which
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/17172#discussion_r105246532
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/objects.scala ---
@@ -216,10 +217,39 @@ case class MapElementsExec(
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17202
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/17120
---
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 xwu0226 commented on the issue:
https://github.com/apache/spark/pull/16626
@gatorsmile yes. I will do so. 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17226
**[Test build #74274 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74274/testReport)**
for PR 17226 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17120
LGTM. 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 aray opened a pull request:
https://github.com/apache/spark/pull/17226
[SPARK-19882][SQL] Pivot with null as a distinct pivot value throws NPE
## What changes were proposed in this pull request?
Allows null values of the pivot column to be included in the pivot
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17133
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/17091
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17133
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 wishes so,
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17091
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 wishes so,
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17175#discussion_r105240101
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicPhysicalOperators.scala
---
@@ -78,9 +78,42 @@ case class ProjectExec(projectList:
Github user JasonMWhite commented on the issue:
https://github.com/apache/spark/pull/17200
Thanks @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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/17200
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17200
thanks, merging to master/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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17172#discussion_r105236895
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/objects.scala ---
@@ -216,10 +217,39 @@ case class MapElementsExec(
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17172#discussion_r105237069
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetBenchmark.scala ---
@@ -165,11 +208,23 @@ object DatasetBenchmark {
val numRows =
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17172#discussion_r105236823
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/objects.scala ---
@@ -216,10 +217,39 @@ case class MapElementsExec(
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17189
@hustfxj Looks pretty good. Could you update the PR title and description
to reflect the latest changes?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/17189#discussion_r105236522
--- Diff: core/src/main/scala/org/apache/spark/deploy/worker/Worker.scala
---
@@ -62,8 +62,8 @@ private[deploy] class Worker(
private val
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15363
**[Test build #74273 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74273/testReport)**
for PR 15363 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15363
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 amitsela commented on a diff in the pull request:
https://github.com/apache/spark/pull/17179#discussion_r105230719
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/MapGroupsWithStateSuite.scala
---
@@ -83,6 +88,34 @@ class MapGroupsWithStateSuite
Github user amitsela commented on a diff in the pull request:
https://github.com/apache/spark/pull/17179#discussion_r105228392
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/KeyedState.scala ---
@@ -61,25 +65,49 @@ import
Github user amitsela commented on a diff in the pull request:
https://github.com/apache/spark/pull/17179#discussion_r105227799
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/KeyedState.scala ---
@@ -61,25 +65,49 @@ import
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17139
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/17139
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74270/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17139
**[Test build #74270 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74270/testReport)**
for PR 17139 at commit
Github user amitsela commented on a diff in the pull request:
https://github.com/apache/spark/pull/17179#discussion_r105224804
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/KeyValueGroupedDataset.scala ---
@@ -230,16 +231,19 @@ class KeyValueGroupedDataset[K, V]
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16626
Maybe you can resolve the conflict now?
---
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/17207
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/17207
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74271/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17207
**[Test build #74271 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74271/testReport)**
for PR 17207 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15009
**[Test build #74272 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74272/testReport)**
for PR 15009 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/15009
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 so,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17055
I will review it today. 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17225
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 dongjinleekr opened a pull request:
https://github.com/apache/spark/pull/17225
[CORE] Support ZStandard Compression
## What changes were proposed in this pull request?
Hadoop will support ZStandard Compression from 2.9.0. This update enables
saving a file in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17207
**[Test build #74271 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74271/testReport)**
for PR 17207 at commit
Github user keypointt commented on the issue:
https://github.com/apache/spark/pull/17207
Jenkins, retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user keypointt commented on the issue:
https://github.com/apache/spark/pull/17207
Jenkins retest it 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
Github user jinxing64 commented on the issue:
https://github.com/apache/spark/pull/17133
@vanzin @srowen
I refined according to the comments, please take a look when you have time
:)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jinxing64 commented on the issue:
https://github.com/apache/spark/pull/16867
@kayousterhout @squito @mridulm
I refined according comments. Please take a look when you have time :)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user nsyca commented on the issue:
https://github.com/apache/spark/pull/17138
I'd start with my definition of a cost-based optimizer (CBO). Cost-based
optimizer is a process where an optimal execution plan is chosen based on its
estimated cost of execution. The estimated cost
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17139
**[Test build #74270 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74270/testReport)**
for PR 17139 at commit
Github user blrnw3 commented on the issue:
https://github.com/apache/spark/pull/17213
Will add doctest and check linting.
Have added before/after error messages to the PR description
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user blrnw3 commented on the issue:
https://github.com/apache/spark/pull/17213
Ah yes it seems `SPARK-19507` is a duplicate. My mistake. In any case I'm
sure this PR satisfies that ticket
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17189
**[Test build #74266 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74266/testReport)**
for PR 17189 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17189
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74266/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17189
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/17192
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/17224
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74269/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17224
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/17224
**[Test build #74269 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74269/testReport)**
for PR 17224 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17192
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74268/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17192
**[Test build #74268 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74268/testReport)**
for PR 17192 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17192
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/17192
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74267/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17192
**[Test build #74267 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74267/testReport)**
for PR 17192 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/10307
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74265/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/10307
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/10307
**[Test build #74265 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74265/testReport)**
for PR 10307 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17055
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74264/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17055
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/17055
**[Test build #74264 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74264/testReport)**
for PR 17055 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17055
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74263/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17055
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/17055
**[Test build #74263 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74263/testReport)**
for PR 17055 at commit
Github user hustfxj commented on the issue:
https://github.com/apache/spark/pull/16450
@srowen @andrewor14 can you see it again?
---
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 hustfxj commented on the issue:
https://github.com/apache/spark/pull/16525
@srowen @andrewor14 can you review it again? Thank you
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17224
**[Test build #74269 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74269/testReport)**
for PR 17224 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/17224
[SPARK-19882][SQL] Pivot with null as the pivot value throws NPE
## What changes were proposed in this pull request?
This PR fixes two problems as below:
Actually, there are
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17192
**[Test build #74268 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74268/testReport)**
for PR 17192 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17192
**[Test build #74267 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74267/testReport)**
for PR 17192 at commit
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/17055
@gatorsmile I have merged with masterï¼if it is ok, could you help to
merge it?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17087
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/17087
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74262/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17087
**[Test build #74262 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74262/testReport)**
for PR 17087 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17055
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74261/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17055
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/17055
**[Test build #74261 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74261/testReport)**
for PR 17055 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17202
cc @srowen and @zsxwing
---
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/17189
**[Test build #74266 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74266/testReport)**
for PR 17189 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/10307
**[Test build #74265 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74265/testReport)**
for PR 10307 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17120
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74260/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17120
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/17120
**[Test build #74260 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74260/testReport)**
for PR 17120 at commit
301 - 400 of 491 matches
Mail list logo
