Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16715
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16944
**[Test build #72959 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72959/testReport)**
for PR 16944 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16932
The final code change doesn't assume Hadoop 2.6 right?
---
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/16932
> The final code change doesn't assume Hadoop 2.6 right?
Right.
---
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/16715#discussion_r101418597
--- Diff:
examples/src/main/java/org/apache/spark/examples/ml/JavaBucketedRandomProjectionLSHExample.java
---
@@ -35,8 +35,15 @@
import
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16534
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72966/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16534
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/16932
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16534
**[Test build #72966 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72966/testReport)**
for PR 16534 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16935
---
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/16932
Since this change is minor and safe, I also cherry-picked to 2.1 to avoid
merge conflicts in future.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16932
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16945
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/16945
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72965/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16945
**[Test build #72965 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72965/testReport)**
for PR 16945 at commit
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/16923#discussion_r101417697
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -106,21 +106,31 @@ private[hive] class HiveClientImpl(
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/16923#discussion_r101417534
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -106,21 +106,31 @@ private[hive] class HiveClientImpl(
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16739
Hi, @felixcheung .
While backporting,
https://github.com/apache/spark/commit/6c35399068f1035fec6d5f909a83a5b1683702e0#diff-3d2a6b9d2b7d84ae179d7ea0f9eca696R1232
seems to break the build
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16946
**[Test build #72967 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72967/testReport)**
for PR 16946 at commit
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/16946
[SPARK-19554][UI,YARN] Allow SHS URL to be used for tracking in YARN RM.
Allow an application to use the History Server URL as the tracking
URL in the YARN RM, so there's still a link to the web
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16938
I think in CTASï¼it is not allowed an existed tableï¼ no strict for the
path exists. In DataFrameWriter.save with errorifnotexist modeï¼path existed
is not allowed.
---
If your project is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16932
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72954/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16898
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/16932
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/16898
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72955/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16898
**[Test build #72955 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72955/testReport)**
for PR 16898 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16932
**[Test build #72954 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72954/testReport)**
for PR 16932 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16534
**[Test build #72966 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72966/testReport)**
for PR 16534 at commit
Github user cherryii commented on the issue:
https://github.com/apache/spark/pull/9608
Was anything similar to this implemented in spark 2? I'm trying to run in a
similar situation and can't seem to get spark to work.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16534
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
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16534
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72949/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16534
**[Test build #72949 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72949/testReport)**
for PR 16534 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16811
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72961/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16811
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/16811
**[Test build #72961 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72961/testReport)**
for PR 16811 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16915
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72952/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16915
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/16915
**[Test build #72952 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72952/testReport)**
for PR 16915 at commit
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/16774
I'd say coming up with a heuristic or algorithm to automatically set the
parallel execution param is going to be pretty challenging, since it depends on
the details of the individual pipeline
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16943
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72950/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16943
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/16943
**[Test build #72950 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72950/testReport)**
for PR 16943 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16945
**[Test build #72965 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72965/testReport)**
for PR 16945 at commit
GitHub user wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/16945
[SPARK-19616][SparkR]:weightCol and aggregationDepth should be improved for
some SparkR APIs
## What changes were proposed in this pull request?
This is a follow-up PR of #16800
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16909
**[Test build #72964 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72964/testReport)**
for PR 16909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16715
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72956/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16715
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/16715
**[Test build #72956 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72956/testReport)**
for PR 16715 at commit
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/16935
Seems I cannot merge now... Will try again later.
---
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 liancheng commented on the issue:
https://github.com/apache/spark/pull/16935
Merging to master an 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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16924#discussion_r101403013
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/EventLoggingListener.scala ---
@@ -137,7 +138,13 @@ private[spark] class EventLoggingListener(
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16936
(There is no detail in the JIRA that you point to.) I think we already
discussed this in part? this duplicates some logic about how cluster resource
management works. Does it really not work if not
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/16935
ok. Nothing new to add. I will merge this to master and branch-2.1 (in case
we want to debug any python test hanging issue in branch-2.1).
---
If your project is set up for it, you can reply to this
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16811
AFAIK Jenkins won't listen to me or Yanbo. We tried couple times with other
PRs - can try again next time.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16909
**[Test build #72963 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72963/testReport)**
for PR 16909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16934
**[Test build #72962 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72962/testReport)**
for PR 16934 at commit
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16934
@zsxwing Left one comment for tests and a question.
It would be great if you could also post a snippet of the plans after this
fix.
---
If your project is set up for it, you can reply to this
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/16942
Weird. I think I've seen that behavior once before. But I think the only
time I force push on a PR is to rebase. Maybe that's the only kind of force
push allowed for Github PRs.
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16895
**[Test build #72960 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72960/testReport)**
for PR 16895 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16811
**[Test build #72961 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72961/testReport)**
for PR 16811 at commit
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16934#discussion_r101398714
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/commands.scala
---
@@ -121,3 +121,25 @@ case class ExplainCommand(
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16934#discussion_r101398532
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamSuite.scala ---
@@ -277,10 +279,22 @@ class StreamSuite extends StreamTest {
Github user budde commented on the issue:
https://github.com/apache/spark/pull/16942
@mallman If I did close it then it was by mistake. The "Reopen and comment"
button was disabled with a message about the PR being closed by a force push
when I hovered over it. Afraid I'm a bit of a
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16811
Hm you should be able to restart it by asking here. If it doesn't it may be
stuck or busy. You can also trigger at spark-prs.appspot.com
---
If your project is set up for it, you can reply to this
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16811
Jenkins add to whitelist
---
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/16944
**[Test build #72959 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72959/testReport)**
for PR 16944 at commit
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/16942
Force pushing your branch shouldn't close the PR. You didn't close it
manually?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16937
I am OK with closing these purely because they're inactive, and, it's
trivial to reopen one if desired. PRs ought to reach a resolution rapidly.
Ideally, if the resolution seems to be that
Github user budde commented on the issue:
https://github.com/apache/spark/pull/16944
Re-pinging participants from #16797: @gatorsmile, @viirya, @ericl, @mallman
and @cloud-fan. Sorry for the noise.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user budde opened a pull request:
https://github.com/apache/spark/pull/16944
[SPARK-19611][SQL] Introduce configurable table schema inference
*Update: Accidentally broke #16942 via a force push. Opening a replacement
PR.*
Replaces #16797. See the discussion in this
Github user budde commented on the issue:
https://github.com/apache/spark/pull/16942
Accidentally did a force-push to my branch for this issue. Looks like I'll
have to open a new PR...
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16920
Oh, if this is asking people to repeat the JIRA link in the description,
then, no I don't agree with that.
---
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/16934
**[Test build #72957 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72957/testReport)**
for PR 16934 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16892
**[Test build #72958 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72958/testReport)**
for PR 16892 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16620
LGTM pending one last comment improvement
---
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/16934
Good question. Make me realize my fix was wrong. We cannot use
`logicalPlan` here because it's not the runtime batch plan. The purpose of
adding StreamingQuery.explain is to allow the user to see
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16892
Jenkins retest this please (filed
https://issues.apache.org/jira/browse/SPARK-19613 for the flaky test)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/16620#discussion_r101392190
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1181,15 +1181,34 @@ class DAGScheduler(
case
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16892
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/16892
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72948/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16892
**[Test build #72948 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72948/testReport)**
for PR 16892 at commit
Github user budde closed the pull request at:
https://github.com/apache/spark/pull/16942
---
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/16537
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/16537
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72953/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16537
**[Test build #72953 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72953/testReport)**
for PR 16537 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16715
**[Test build #72956 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72956/testReport)**
for PR 16715 at commit
Github user budde commented on the issue:
https://github.com/apache/spark/pull/16942
Tests appear to be failing due to the following error:
```
[info] Exception encountered when attempting to run a suite with class
name:
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16672#discussion_r101388447
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/command/DDLSuite.scala
---
@@ -1816,4 +1816,123 @@ class DDLSuite extends QueryTest
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16898
**[Test build #72955 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72955/testReport)**
for PR 16898 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16844
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72946/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16844
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16672#discussion_r101388054
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/command/DDLSuite.scala
---
@@ -1816,4 +1816,123 @@ class DDLSuite extends QueryTest
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16844
**[Test build #72946 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72946/testReport)**
for PR 16844 at commit
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16934
This solution is okay. I'm just not sure why we use
`lastExecution.logicalPlan` instead of `logicalPlan` directly. In that case, we
wouldn't need the `streaming = true` option for `ExplainCommand`
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16942
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72947/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16942
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 brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16934#discussion_r101387562
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamExecution.scala
---
@@ -673,7 +673,7 @@ class StreamExecution(
if
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16932
**[Test build #72954 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72954/testReport)**
for PR 16932 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16750
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16942
**[Test build #72947 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72947/testReport)**
for PR 16942 at commit
201 - 300 of 587 matches
Mail list logo
