Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17498
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/17498
**[Test build #3632 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3632/testReport)**
for PR 17498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17498
**[Test build #3632 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3632/testReport)**
for PR 17498 at commit
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17498
@srowen @jerryshao
If a spark application developer, using event compress, from the spark
official document, will not see the use of spark.io.compression.codec is
specified compression
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17498
@jerryshao
This is just an optimization suggestion.
---
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 guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17498
@srowen i add a space
---
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/17498
IMHO I thought this is still a unnecessary fix. I would doubt if user
really get confused without your fix? You can always correct me since I stand
on the of developers :).
---
If your project
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17498
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 project does not have this
