Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10529#issuecomment-168152257
OK to test
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10513#issuecomment-168158630
If we are creating our own Optional, why don't we also support all the
methods available on Guava, so we only need to break "import" compatibility?
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10390#issuecomment-168150125
**[Test build #48547 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48547/consoleFull)**
for PR 10390 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168154343
**[Test build #48549 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48549/consoleFull)**
for PR 10525 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10513#issuecomment-168158788
My theory was that it makes it more compatible with Java 8 Optional. Later,
moving to its implementation is a smaller change. We're taking the bigger
change now. Or at
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8785#issuecomment-168148505
**[Test build #2280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2280/consoleFull)**
for PR 8785 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10533#issuecomment-168157967
I've merged 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 catap commented on the pull request:
https://github.com/apache/spark/pull/4456#issuecomment-168152178
@rxin, ok, I will
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-168152168
Found a related HIVE JIRA to support the left anti join:
https://issues.apache.org/jira/browse/HIVE-12519
However, their proposed solution has a hole.
Github user vectorijk commented on a diff in the pull request:
https://github.com/apache/spark/pull/10489#discussion_r48650445
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/mathExpressions.scala
---
@@ -279,6 +330,9 @@ object Factorial {
)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10459#issuecomment-168148715
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/10459#issuecomment-168148675
**[Test build #48545 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48545/consoleFull)**
for PR 10459 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10459#issuecomment-168148714
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-168149596
@yanboliang Because that test doesn't fail so this commit doesn't set
`TripletFields.All` there. However, I tried it and it also passes the test. Do
you think we
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10390#issuecomment-168153873
**[Test build #48548 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48548/consoleFull)**
for PR 10390 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9267#issuecomment-168150628
**[Test build #48546 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48546/consoleFull)**
for PR 9267 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10390#issuecomment-168150652
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/10390#issuecomment-168150653
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/10539#issuecomment-168150722
@viirya I'm not very familiar with GraphX and I just found they are do the
same thing for different interface. Maybe we can hear others' opinions.
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9267#issuecomment-168150715
Test PASSed.
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/9267#issuecomment-168150714
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10390#issuecomment-168150645
**[Test build #48547 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48547/consoleFull)**
for PR 10390 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10532
---
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/10529#discussion_r48651665
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Catalog.scala
---
@@ -104,7 +104,7 @@ class SimpleCatalog(val conf: CatalystConf)
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10533
---
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/10532#issuecomment-168158419
I've merged 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 rxin commented on the pull request:
https://github.com/apache/spark/pull/10459#issuecomment-168148942
I've merged it. 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10540#issuecomment-168181589
**[Test build #48551 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48551/consoleFull)**
for PR 10540 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168184217
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/10525#issuecomment-168184213
**[Test build #48553 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48553/consoleFull)**
for PR 10525 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168184215
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/10540#issuecomment-168192401
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 hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168194460
@JoshRosen these builds fail often and non-deterministically with a **fails
build dependency** tests. The problem is that I cannot find the cause of this
problem
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168208226
**[Test build #48555 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48555/consoleFull)**
for PR 10525 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168210083
**[Test build #48557 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48557/consoleFull)**
for PR 10525 at commit
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168182227
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168178455
**[Test build #48550 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48550/consoleFull)**
for PR 10525 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168182029
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/10525#issuecomment-168182024
**[Test build #48552 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48552/consoleFull)**
for PR 10525 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168182027
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/10525#issuecomment-168184101
**[Test build #48553 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48553/consoleFull)**
for PR 10525 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168190691
When running any test suite that extends `HiveComparisonTest`, detail logs
can be found in `sql/hive/target/unit-tests.log`. If a query string is
convertible, we
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168191048
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
Github user thomastechs commented on a diff in the pull request:
https://github.com/apache/spark/pull/10529#discussion_r48653675
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Catalog.scala
---
@@ -104,7 +104,7 @@ class SimpleCatalog(val conf:
Github user thomastechs commented on the pull request:
https://github.com/apache/spark/pull/10529#issuecomment-168173475
@rxin I have updated the style check difference ,you mentioned. and
committed to my branch. And I see it is reflected here in this same pull
request. Please
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/10540#issuecomment-168179906
Hit this issue while working on canonicalized native view support.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168179937
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168208273
Test PASSed.
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/10525#issuecomment-168208271
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 hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168174676
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168174246
Test PASSed.
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/10525#issuecomment-168174243
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/10525#issuecomment-168178889
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/10525#issuecomment-168178887
**[Test build #48550 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48550/consoleFull)**
for PR 10525 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168178890
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/10541#issuecomment-168191248
**[Test build #48554 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48554/consoleFull)**
for PR 10541 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168191293
**[Test build #48555 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48555/consoleFull)**
for PR 10525 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10540#issuecomment-168192337
**[Test build #48551 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48551/consoleFull)**
for PR 10540 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10540#issuecomment-168192402
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168209143
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10390#issuecomment-168165273
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/10390#issuecomment-168165278
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/10390#issuecomment-168165009
**[Test build #48548 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48548/consoleFull)**
for PR 10390 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168174120
**[Test build #48549 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48549/consoleFull)**
for PR 10525 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168194609
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 brkyvz commented on the pull request:
https://github.com/apache/spark/pull/10453#issuecomment-168194624
@zsxwing Thanks! 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168194592
**[Test build #48554 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48554/consoleFull)**
for PR 10541 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168194610
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user robbinspg commented on the pull request:
https://github.com/apache/spark/pull/10421#issuecomment-168172679
re-merged with latest master
Please retest
---
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/10540
[SPARK-12592][SQL][TEST] Don't mute Spark loggers in TestHive.reset()
There's a hack done in `TestHive.reset()`, which intended to mute noisy
Hive loggers. However, Spark testing loggers are
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168181912
**[Test build #48552 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48552/consoleFull)**
for PR 10525 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/10541
[SPARK-12592][SQL][WIP] Converts resolved logical plan back to SQL
This PR tries to enable Spark SQL to convert resolved logical plans back to
SQL query strings. For now, the major use case is
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168191297
I found SQL generation in Slick can be a good reference for attacking
limitations mentioned in the PR description. But the current approach should be
enough for
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10522#discussion_r48660161
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -203,15 +203,15 @@ class Analyzer(
*
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10522#discussion_r48660142
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -190,7 +190,7 @@ class Analyzer(
*
Github user FlytxtRnD closed the pull request at:
https://github.com/apache/spark/pull/7320
---
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 tribbloid commented on the pull request:
https://github.com/apache/spark/pull/8785#issuecomment-168211061
Looks like the removed qualifier of Map in JDBCRelation has caused build to
fail (Map is cast to immutable.Map). I'm adding back the qualifier
scala.collection.Map
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168211120
**[Test build #48558 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48558/consoleFull)**
for PR 10541 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168211126
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/10541#issuecomment-168211125
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/10525#issuecomment-168234676
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/10525#issuecomment-168234675
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/10525#issuecomment-168234652
**[Test build #48557 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48557/consoleFull)**
for PR 10525 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168220607
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/10541#issuecomment-168220278
**[Test build #48558 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48558/consoleFull)**
for PR 10541 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168220603
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 FlytxtRnD commented on the pull request:
https://github.com/apache/spark/pull/7320#issuecomment-168222327
@jkbradley Thank you for the review. I will close this issue and will
surely help in testing the other PR. Also it would be great if you could take a
look at #6880
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168240969
I have a few hunches about what could be causing the dependency manifest
checking problems. I'll keep investigating when I get home later tonight. I
think I've
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10421#issuecomment-168259354
**[Test build #2282 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2282/consoleFull)**
for PR 10421 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10529#issuecomment-168259243
**[Test build #2281 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2281/consoleFull)**
for PR 10529 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168259081
Should we revert that dependency check thing first?
---
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 gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10542
[SPARK-12594] [SQL] Outer Join Conversion: Outer/Right/Left to Inner and
Outer to Left/Right
Conversion of outer joins, if the local predicates can restrict the result
sets so that all
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10542#issuecomment-168269686
**[Test build #48559 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48559/consoleFull)**
for PR 10542 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168278782
Aha! It appears that there _is_ a portability issue in `sort`, or at least
in how we're using it in the dependency-checking script.
When I run `echo -e
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10452#issuecomment-168271940
**[Test build #2283 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2283/consoleFull)**
for PR 10452 at commit
Github user sureshthalamati commented on the pull request:
https://github.com/apache/spark/pull/10452#issuecomment-168260505
Thanks, Michael. Updated the PR. Please review.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10452#issuecomment-168259705
**[Test build #2283 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2283/consoleFull)**
for PR 10452 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10529#issuecomment-168261528
**[Test build #2281 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2281/consoleFull)**
for PR 10529 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10421#issuecomment-168268755
**[Test build #2282 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2282/consoleFull)**
for PR 10421 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10543#issuecomment-168279632
Actually, it occurred to me that I should really be setting `LC_ALL=C` at
the top of the script to guard against future problems in case we add
additional
1 - 100 of 139 matches
Mail list logo
