Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12620#issuecomment-214147661
@njwhite We still use PickleSerializer to deserialize the functions, so it
means the serializer MUST be compatible with Pickle, I'm not sure make it
configurable will
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12651
---
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/12648
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12651#issuecomment-214147253
LGTM,
Merging this into master, 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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12648#issuecomment-214147129
Merging this into master, 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11635#issuecomment-214146689
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11635#issuecomment-214146694
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11635#issuecomment-214146456
**[Test build #56875 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56875/consoleFull)**
for PR 11635 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/10262#issuecomment-214143879
@huaxingao Do you mind If I submit a PR based on this if you are not
working on this? (It looks it has been inactive for few months!)
---
If your project is set
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214139743
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-214139613
Also we should NOT depend on Hive config values.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214139748
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12081#discussion_r60863754
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -121,8 +123,11 @@ class SessionCatalog(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214139137
**[Test build #56871 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56871/consoleFull)**
for PR 12493 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12081#discussion_r60863712
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveSessionCatalog.scala ---
@@ -75,9 +76,22 @@ private[sql] class HiveSessionCatalog(
// |
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214138319
Oh, my bad. Today, I tried again to implement DecimalAggregate optimizer
for Windows again and handled to implement it. Last week, I think I made some
mistake
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10521#issuecomment-214138012
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-214138038
@gatorsmile the new DDLs shouldn't go to the Hive package. We should put
all the DDLs in the sql/core package.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10521#issuecomment-214138016
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10521#issuecomment-214137781
**[Test build #56882 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56882/consoleFull)**
for PR 10521 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12641#issuecomment-214137576
**[Test build #2866 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2866/consoleFull)**
for PR 12641 at commit
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/12066#issuecomment-214136838
@jkbradley Thanks for your comments, please see my inline reply to your
concerns. Because there are no attributes were stored in label column metadata
of
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12649#issuecomment-214135532
Thank you for merging, @shivaram .
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10521#issuecomment-214134771
**[Test build #56882 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56882/consoleFull)**
for PR 10521 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12090#issuecomment-214134982
@sun-rui Can we close this PR or will we make more updates on this ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214134785
**[Test build #56881 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56881/consoleFull)**
for PR 12421 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12649
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/12648#issuecomment-214134616
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12649#issuecomment-214133454
LGTM. Merging this
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user rajeshbalamohan commented on the pull request:
https://github.com/apache/spark/pull/12319#issuecomment-214132553
Thanks @liancheng , @rxin
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12658#issuecomment-214132429
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-214132079
**[Test build #56880 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56880/consoleFull)**
for PR 12618 at commit
GitHub user vishnu667 opened a pull request:
https://github.com/apache/spark/pull/12658
[Spark 14653][WIP][Mllib]
## What changes were proposed in this pull request?
Inorder to remove Jackson and numeric parser from the mllib-local's
dependencies. I've added two
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12649#issuecomment-214132007
Thank you, @felixcheung !
---
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
Github user maropu closed the pull request at:
https://github.com/apache/spark/pull/11046
---
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 maropu commented on the pull request:
https://github.com/apache/spark/pull/11046#issuecomment-214131383
Close this for now and, if needed, I'll reopen 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12656#issuecomment-214131326
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10631#issuecomment-214131211
Close this for now and, if needed, I'll reopen 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
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10523#issuecomment-214131130
Close this for now and, if needed, I'll reopen 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12656#issuecomment-214131324
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
Github user maropu closed the pull request at:
https://github.com/apache/spark/pull/10631
---
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 pull request:
https://github.com/apache/spark/pull/12204#issuecomment-214131108
**[Test build #56879 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56879/consoleFull)**
for PR 12204 at commit
Github user maropu closed the pull request at:
https://github.com/apache/spark/pull/10523
---
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 pull request:
https://github.com/apache/spark/pull/12656#issuecomment-214131077
**[Test build #56870 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56870/consoleFull)**
for PR 12656 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12204#issuecomment-214131007
ping @yhuai @marmbrus @cloud-fan @rxin I think this might be a bit related
to DDL support. Can you please review this? Thanks.
---
If your project is set up for it,
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12655#discussion_r60862612
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -322,6 +322,59 @@ class DAGSchedulerSuite extends SparkFunSuite with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12204#issuecomment-214130299
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12649#issuecomment-214130308
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12204#issuecomment-214130301
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12649#issuecomment-214130310
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12204#issuecomment-214130297
**[Test build #56878 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56878/consoleFull)**
for PR 12204 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12649#issuecomment-214130277
**[Test build #56876 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56876/consoleFull)**
for PR 12649 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12652#issuecomment-214130202
**[Test build #56877 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56877/consoleFull)**
for PR 12652 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12204#issuecomment-214130199
**[Test build #56878 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56878/consoleFull)**
for PR 12204 at commit
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/12649#issuecomment-214130171
looks 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-214130068
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-214130069
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-214129992
**[Test build #56872 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56872/consoleFull)**
for PR 12081 at commit
Github user hbhanawat commented on the pull request:
https://github.com/apache/spark/pull/12641#issuecomment-214129927
Looks like the failing test is related to this JIRA: SPARK-13693. I have
reopened it.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12066#issuecomment-214127358
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12066#issuecomment-214127359
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12066#issuecomment-214127204
**[Test build #56874 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56874/consoleFull)**
for PR 12066 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12641#issuecomment-214126461
**[Test build #2865 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2865/consoleFull)**
for PR 12641 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12649#issuecomment-214124731
**[Test build #56876 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56876/consoleFull)**
for PR 12649 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12649#discussion_r60861763
--- Diff: docs/sql-programming-guide.md ---
@@ -1138,16 +1138,16 @@ for teenName in teenNames.collect():
schemaPeople # The DataFrame from the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11635#issuecomment-214122981
**[Test build #56875 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56875/consoleFull)**
for PR 11635 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214122523
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214122524
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214122275
**[Test build #56868 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56868/consoleFull)**
for PR 12655 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/11635#discussion_r60861439
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/FilterPushdownSuite.scala
---
@@ -758,4 +758,217 @@ class
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/11635#discussion_r60861437
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/FilterPushdownSuite.scala
---
@@ -758,4 +758,217 @@ class
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/12649#discussion_r60861420
--- Diff: docs/sql-programming-guide.md ---
@@ -1138,16 +1138,16 @@ for teenName in teenNames.collect():
schemaPeople # The DataFrame from the previous
Github user nirandaperera commented on the pull request:
https://github.com/apache/spark/pull/12506#issuecomment-214120146
@BryanCutler I was looking for some unit tests which could simulate this
scenario in the Master.scala class, but I couldn't find any. But i think I can
reproduce
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-214120098
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-214120097
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-214119972
**[Test build #56869 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56869/consoleFull)**
for PR 12618 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12066#issuecomment-214119856
**[Test build #56874 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56874/consoleFull)**
for PR 12066 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12612#discussion_r60861038
--- Diff: core/src/main/scala/org/apache/spark/Accumulator.scala ---
@@ -17,121 +17,281 @@
package org.apache.spark
+import java.{lang =>
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12612#discussion_r60860997
--- Diff: core/src/main/scala/org/apache/spark/executor/TaskMetrics.scala
---
@@ -287,11 +258,10 @@ private[spark] object TaskMetrics extends Logging {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214118512
**[Test build #56873 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56873/consoleFull)**
for PR 12655 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12612#discussion_r60860782
--- Diff: core/src/main/scala/org/apache/spark/executor/TaskMetrics.scala
---
@@ -287,11 +258,10 @@ private[spark] object TaskMetrics extends Logging {
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12654
---
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 pull request:
https://github.com/apache/spark/pull/12632#issuecomment-214116801
Thank you, @rxin .
For the Java Linter, I'll keep in mind and try to fix in another way.
---
If your project is set up for it, you can reply to this email
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12651#discussion_r60860719
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/test/SQLTestData.scala ---
@@ -103,6 +103,19 @@ private[sql] trait SQLTestData { self =>
df
Github user sajeevm closed the pull request at:
https://github.com/apache/spark/pull/12657
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12654#issuecomment-214116696
Note that they are not the same for UDTs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12654#issuecomment-214116709
LGTM - 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12657#issuecomment-214116669
Can you close this pull request?
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12657#issuecomment-214115543
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12632
---
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 sajeevm opened a pull request:
https://github.com/apache/spark/pull/12657
Branch 1.6
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explain how this
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12632#issuecomment-214115325
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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12632#issuecomment-214114869
Hi, @rxin .
I'm not sure when we can turn on Jenkins Linter again.
Could you merge this PR without that?
---
If your project is set up for it, you can
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/12581#issuecomment-214106380
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12629#issuecomment-214105426
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12629#issuecomment-214105430
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12629#issuecomment-214104876
**[Test build #56867 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56867/consoleFull)**
for PR 12629 at commit
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/12620#issuecomment-214104132
If we do end up adding this we would probably want to add a test of using a
custom serializer (but maybe don't rush to do this since I think if we want to
expose this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-214104242
**[Test build #56872 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56872/consoleFull)**
for PR 12081 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-214103737
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
1 - 100 of 370 matches
Mail list logo
