Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16098
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69606/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69606 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69606/consoleFull)**
for PR 16098 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16098
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/16125
**[Test build #69607 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69607/consoleFull)**
for PR 16125 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15795
**[Test build #69612 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69612/consoleFull)**
for PR 15795 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15795
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69612/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69614 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69614/consoleFull)**
for PR 16098 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15795
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16068
We have a rule
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16128
**[Test build #69609 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69609/consoleFull)**
for PR 16128 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16068#discussion_r90752814
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveUDFSuite.scala
---
@@ -487,6 +488,29 @@ class HiveUDFSuite extends QueryTest
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16127
I didn't actually look at the content. I thought they were bug fixes and as
a result said we should backport them. The title and description of the
original pr implied they were bug fixes.
---
If
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16126
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
I will close this 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
enabled and
Github user dongjoon-hyun closed the pull request at:
https://github.com/apache/spark/pull/16127
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
I see. If then, it's my fault.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/15813
Merging in 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, or
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16030
That is something I tried to standardize. I think we should standardize it,
otherwise it is very confusing. I think it's the right thing to do. I just
don't want people's production jobs
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16030
@brkyvz yea, I think so, but the issue of column ordering seems to be out
of scope in this original ticket. So, why don't we open a new jira and discuss
there?
---
If your project is set up for
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15795
**[Test build #69613 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69613/consoleFull)**
for PR 15795 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/15813
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/15813#discussion_r90751405
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVFileFormat.scala
---
@@ -173,51 +179,37 @@ class CSVFileFormat extends
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/15795
I found myself wanting to make a number of tiny comments, so I thought it'd
be easier to send a PR. Could you please take a look at this one?
Thanks!
---
If your project is set up for it,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16120
**[Test build #69610 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69610/consoleFull)**
for PR 16120 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16125
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69607/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16125
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 brkyvz commented on the issue:
https://github.com/apache/spark/pull/16030
Looks great! Thanks so much @maropu . @tdas or @liancheng would you mind
taking a last look and possibly merging to 2.1?
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15795
**[Test build #69612 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69612/consoleFull)**
for PR 15795 at commit
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16090
Seems like the caching broke a bunch of tests. I'll take a look at this
again tomorrow.
On Fri, Dec 2, 2016, 7:49 PM UCB AMPLab wrote:
> Test FAILed.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16126
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69599/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16126
**[Test build #69599 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69599/consoleFull)**
for PR 16126 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16126
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16021
Thank you all so much for giving your attentions and opinions here.
I asked the one which is not allowed here. Please refer #16127 for more
details, too.
I'm closing this
Github user dongjoon-hyun closed the pull request at:
https://github.com/apache/spark/pull/16021
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16128
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/16128
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69609/
Test PASSed.
---
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16126
Merging in 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, or
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16113#discussion_r90751494
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/OffsetSeq.scala
---
@@ -54,6 +61,26 @@ object OffsetSeq {
* `nulls` in the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16120
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69608/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16120
**[Test build #69608 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69608/consoleFull)**
for PR 16120 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16120
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16128#discussion_r90752217
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/streaming/OffsetSeqLogSuite.scala
---
@@ -60,4 +60,39 @@ class OffsetSeqLogSuite extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16030
**[Test build #69611 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69611/consoleFull)**
for PR 16030 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15795
**[Test build #69613 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69613/consoleFull)**
for PR 15795 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15795
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69613/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15795
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/16128
**[Test build #69609 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69609/consoleFull)**
for PR 16128 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15923
cc @zsxwing @JoshRosen does this look good?
---
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 eyalfa commented on the issue:
https://github.com/apache/spark/pull/16043
Will do.
I'm currently focusing on a functional issue with simplifying operations on
createMap, I'll take care of these while on it.
On Dec 2, 2016 11:09 PM, "Xiao Li"
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16030#discussion_r90752283
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -189,7 +189,15 @@ case class DataSource(
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16116
Build started: [Tests] `org.apache.spark.repl.ExecutorClassLoaderSuite`
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16090#discussion_r90637793
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
---
@@ -58,13 +58,21 @@ case class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16110
---
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/16116
**[Test build #69561 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69561/consoleFull)**
for PR 16116 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16062
---
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/16112
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 the issue:
https://github.com/apache/spark/pull/15863
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 mridulm commented on the issue:
https://github.com/apache/spark/pull/16098
That looks like a bug in ParquetRecordWriter (the contract of close() is
unambiguous) ... but then, I guess there is no point in fighting against buggy
code : we have to integrate with a lot of
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16062
Merged 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, or
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16116
**[Test build #69566 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69566/consoleFull)**
for PR 16116 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16098#discussion_r90634188
--- Diff:
core/src/main/scala/org/apache/spark/internal/io/SparkHadoopMapReduceWriter.scala
---
@@ -163,12 +163,22 @@ object SparkHadoopMapReduceWriter
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15620
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 HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16098#discussion_r90643022
--- Diff:
core/src/main/scala/org/apache/spark/internal/io/SparkHadoopMapReduceWriter.scala
---
@@ -146,29 +146,32 @@ object SparkHadoopMapReduceWriter
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16098#discussion_r90625904
--- Diff:
core/src/main/scala/org/apache/spark/internal/io/SparkHadoopMapReduceWriter.scala
---
@@ -163,12 +163,22 @@ object SparkHadoopMapReduceWriter
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
Thank you both sincerely. Let me fix it.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16030
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69565/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16030
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 srowen commented on the issue:
https://github.com/apache/spark/pull/16103
Seems reasonable to me too.
---
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/16043
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69564/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16043
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/15863
---
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/16088
---
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/16116
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/16116
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69561/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16030
**[Test build #69567 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69567/consoleFull)**
for PR 16030 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16112
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
Build started: [CORE] `org.apache.spark.JavaAPISuite`
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16107
Seems correct to me, yes.
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/16102
@rxin it's a weird one. This is all I know:
https://issues.apache.org/jira/browse/SPARK-17875
https://github.com/apache/spark/pull/15436
It's unused but couldn't get the Python
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/15994#discussion_r90635187
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameNaFunctions.scala ---
@@ -130,6 +130,13 @@ final class DataFrameNaFunctions private[sql](df:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16115
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/16043
**[Test build #69564 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69564/consoleFull)**
for PR 16043 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16115
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69563/
Test PASSed.
---
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16090
My main concern is that, in `CreateDataSourceTableCommand`, we call
`DataSource.resolveRelation` to infer the schema and partition columns. At that
time, the table is not created yet, so
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/16098
@srowen This is where try-with-resources is really useful in java.
Util.tryWithSafeFinallyAndFailureCallbacks is an attempt at doing that in
scala with mixed results.
I agree, the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16115
**[Test build #69563 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69563/consoleFull)**
for PR 16115 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15620
**[Test build #69569 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69569/consoleFull)**
for PR 15620 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69568 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69568/consoleFull)**
for PR 16098 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16088
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 the issue:
https://github.com/apache/spark/pull/16110
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 Yunni commented on a diff in the pull request:
https://github.com/apache/spark/pull/15795#discussion_r90736546
--- Diff: docs/ml-features.md ---
@@ -1478,3 +1478,139 @@ for more details on the API.
{% include_example python/ml/chisq_selector_example.py %}
Github user wangyum commented on the issue:
https://github.com/apache/spark/pull/16122
@mallman MySQL and version is 5.6.29
---
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/16109
> Test build #3459 has finished for PR 16109 at commit 0901a65.
>
> This patch fails PySpark unit tests.
> This patch merges cleanly.
> This patch adds no public classes.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16125
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69597/
Test FAILed.
---
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16124
Can you please add [Backport-1.6] to the PR title?
---
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/16125
**[Test build #69597 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69597/consoleFull)**
for PR 16125 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16125
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16123
Thanks - merging in master/branch-2.1.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16090
**[Test build #69600 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69600/consoleFull)**
for PR 16090 at commit
1 - 100 of 500 matches
Mail list logo