Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10878#issuecomment-174159956
**[Test build #2448 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2448/consoleFull)**
for PR 10878 at commit
Github user nishkamravi2 commented on a diff in the pull request:
https://github.com/apache/spark/pull/10881#discussion_r50617860
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2183,6 +2183,13 @@ object SparkContext extends Logging {
}
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8734#issuecomment-174160685
**[Test build #49934 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49934/consoleFull)**
for PR 8734 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10828#issuecomment-174162678
**[Test build #2446 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2446/consoleFull)**
for PR 10828 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8734#issuecomment-174165133
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/8734#issuecomment-174165132
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/8734#issuecomment-174165097
**[Test build #49934 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49934/consoleFull)**
for PR 8734 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-174175906
These tests are failing everywhere, it's not related
---
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/10882#issuecomment-174161885
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/10882#issuecomment-174161889
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10585#issuecomment-174177590
I'll take this over if there's no progress on this PR
---
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 pull request:
https://github.com/apache/spark/pull/4402#issuecomment-174185184
@maropu I think this was actually a good change, as we have had these
deprecation warnings for a long time. Do you want to revive this and try to
remove as many usages
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10789#issuecomment-174185228
@tsudukim @tritab if changing directory in controversial, shall we just
focus on solving the quoting problem?
---
If your project is set up for it, you can reply to
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10851#issuecomment-174160987
Going to merge this. Thanks.
Would be great if @cloud-fan can take another look at the implementation.
---
If your project is set up for it, you can reply to
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10851
---
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/10882#issuecomment-174163035
**[Test build #2447 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2447/consoleFull)**
for PR 10882 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10630#issuecomment-174165179
When resolving the conflicts, I realized the multi-children `Union` might
have duplicate `exprId`. So far, I did not add a function to de-duplicate them.
This is
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10867#issuecomment-174176274
Merged to master/1.6
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10867
---
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/10878#issuecomment-174163265
**[Test build #2448 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2448/consoleFull)**
for PR 10878 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10630#issuecomment-174165441
**[Test build #49936 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49936/consoleFull)**
for PR 10630 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10866
---
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 hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10723#discussion_r50619674
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkQl.scala ---
@@ -42,6 +45,95 @@ private[sql] class SparkQl(conf: ParserConf =
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/8734#discussion_r50617823
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -331,12 +336,62 @@ class DecisionTreeSuite extends SparkFunSuite
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10882#issuecomment-174166173
**[Test build #49932 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49932/consoleFull)**
for PR 10882 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10866#issuecomment-174177302
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/10866#issuecomment-174177300
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/10413#issuecomment-174177516
If there's another vote in favor -- and no strong objection surfacing --
I'd like to proceed soon to merge this.
---
If your project is set up for it, you can reply to
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10723#discussion_r50619708
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkQl.scala ---
@@ -52,26 +57,30 @@ private[sql] class SparkQl(conf: ParserConf =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10630#issuecomment-174171695
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/10630#issuecomment-174171694
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/10875#issuecomment-174184611
Seems fine
---
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 pull request:
https://github.com/apache/spark/pull/10865#issuecomment-174165671
Yeah, these are consistent test failures but they're not due to this change.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10807#issuecomment-174176986
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10807
---
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 hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10723#discussion_r50619696
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkQl.scala ---
@@ -42,6 +45,95 @@ private[sql] class SparkQl(conf: ParserConf =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10881#issuecomment-174159853
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/10881#issuecomment-174159854
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10878#issuecomment-174159859
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10851#issuecomment-174160902
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/10882#issuecomment-174166217
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/10882#issuecomment-174166218
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/10630#issuecomment-174171631
**[Test build #49936 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49936/consoleFull)**
for PR 10630 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10873
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/10866#issuecomment-174176845
Merged to master/1.6
---
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 hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10723#discussion_r50619659
--- Diff:
sql/catalyst/src/main/antlr3/org/apache/spark/sql/catalyst/parser/ExpressionParser.g
---
@@ -518,6 +527,10 @@ principalIdentifier
|
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10723#discussion_r50619663
--- Diff:
sql/catalyst/src/main/antlr3/org/apache/spark/sql/catalyst/parser/SparkSqlLexer.g
---
@@ -465,7 +467,7 @@ Identifier
fragment
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10723#issuecomment-174183437
@viirya I did a pass. I have left a few comment for you to address. Overall
this looks pretty good!
---
If your project is set up for it, you can reply to this
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10882#issuecomment-174159461
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 viirya closed the pull request at:
https://github.com/apache/spark/pull/10845
---
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 pull request:
https://github.com/apache/spark/pull/10851#issuecomment-174160904
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/10851#issuecomment-174160855
**[Test build #49929 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49929/consoleFull)**
for PR 10851 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/10873#issuecomment-174172224
O.K, Merging this into `master` and `branch-1.6`. Thanks @ajbozarth !
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10878#issuecomment-174217372
I've merged this. 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10882
---
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/10878
---
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/10882#issuecomment-174217310
Merging this 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/10762#issuecomment-174222027
@hvanhovell can you help review the parser changes?
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10881#issuecomment-174227028
@nishkamravi2 I suggest that you add a new exception RpcEnvStopException
that extends IllegalStateException. Then you can use RpcEnvStopException in
this line:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10568#issuecomment-174227032
**[Test build #49938 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49938/consoleFull)**
for PR 10568 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174227606
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 nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/10881#issuecomment-174230956
Ok, makes sense. Btw, we also want to mask the exception being thrown at
line 161 (I see that in the logs as well).
---
If your project is set up for it, you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174231043
**[Test build #49941 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49941/consoleFull)**
for PR 10883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10568#issuecomment-174236024
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/10568#issuecomment-174235975
**[Test build #49938 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49938/consoleFull)**
for PR 10568 at commit
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10884#discussion_r50627843
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/ErrorPositionSuite.scala ---
@@ -19,20 +19,34 @@ package org.apache.spark.sql.hive
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10885#issuecomment-174243642
**[Test build #49943 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49943/consoleFull)**
for PR 10885 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10886#issuecomment-174244338
**[Test build #49945 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49945/consoleFull)**
for PR 10886 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10865#issuecomment-174219265
looks like it's related to the jenkins machine that run this test?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174228994
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/10883#issuecomment-174228991
**[Test build #49940 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49940/consoleFull)**
for PR 10883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174228992
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/10883#issuecomment-174228908
**[Test build #49940 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49940/consoleFull)**
for PR 10883 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10861#issuecomment-174229596
Can you add more description to explain _how_ this patch reduces the size
of broadcasts? The change isn't obvious to me at first glance, so one or two
sentences of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174232333
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/10883#issuecomment-174232131
**[Test build #49941 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49941/consoleFull)**
for PR 10883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174232331
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/10568#issuecomment-174236022
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 a diff in the pull request:
https://github.com/apache/spark/pull/10884#discussion_r50627893
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/ErrorPositionSuite.scala ---
@@ -19,20 +19,34 @@ package org.apache.spark.sql.hive
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10884#discussion_r50627984
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/ErrorPositionSuite.scala ---
@@ -19,20 +19,34 @@ package org.apache.spark.sql.hive
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10884#discussion_r50627993
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/ErrorPositionSuite.scala ---
@@ -19,20 +19,34 @@ package org.apache.spark.sql.hive
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10885#discussion_r50629043
--- Diff: dev/sparktestsupport/modules.py ---
@@ -15,12 +15,14 @@
# limitations under the License.
#
+from functools import
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10885#discussion_r50629044
--- Diff: dev/run-tests.py ---
@@ -377,12 +382,12 @@ def run_scala_tests_maven(test_profiles):
def run_scala_tests_sbt(test_modules,
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/10886
[SPARK-12624][PYSPARK] Checks row length when converting Java arrays to
Python rows
When actual row length doesn't conform to specified schema field length, we
should give a better error
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10884#issuecomment-174245424
jenkins retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/10886#discussion_r50629567
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/python.scala ---
@@ -220,7 +220,12 @@ object EvaluatePython {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174227604
**[Test build #49939 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49939/consoleFull)**
for PR 10883 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174227570
**[Test build #49939 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49939/consoleFull)**
for PR 10883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174227607
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/10881#issuecomment-174227577
Thanks for the pointers @zsxwing. Makes sense to just log an error message.
Instead of throwing an exception from postMessage and logging it in send, what
if we
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10884#discussion_r50627794
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveComparisonTest.scala
---
@@ -150,7 +150,11 @@ abstract class HiveComparisonTest
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/10885
[SPARK-8725] Test modules in topologically-sorted order in dev/run-tests
This patch improves our `dev/run-tests` script to test modules in a
topologically-sorted order based on modules'
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10881#discussion_r50626484
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2183,6 +2183,13 @@ object SparkContext extends Logging {
}
/**
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10883#issuecomment-174226733
cc @rxin @liancheng
---
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10885#discussion_r50629025
--- Diff: dev/sparktestsupport/toposort.py ---
@@ -0,0 +1,85 @@
+###
+#
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10884#issuecomment-174243493
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/10884#issuecomment-174243409
**[Test build #49942 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49942/consoleFull)**
for PR 10884 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10875#discussion_r50625230
--- Diff: core/src/main/scala/org/apache/spark/io/CompressionCodec.scala ---
@@ -149,12 +149,7 @@ class LZFCompressionCodec(conf: SparkConf) extends
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10875#discussion_r50625235
--- Diff: core/src/main/scala/org/apache/spark/io/CompressionCodec.scala ---
@@ -149,12 +149,7 @@ class LZFCompressionCodec(conf: SparkConf) extends
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10568#issuecomment-174226192
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
1 - 100 of 153 matches
Mail list logo
