Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-154004973
Note this duplicates https://github.com/apache/spark/pull/5622
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-154050466
OK, Josh also closed the other one. One JIRA is open now. At least have <=
1 PR.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user viper-kun closed the pull request at:
https://github.com/apache/spark/pull/9191
---
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 viper-kun commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-154050289
ok. close 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 viper-kun commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-151385025
@JoshRosen
Is it ok? If it doesn't work, I will close this pr.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150769380
**[Test build #1949 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1949/consoleFull)**
for PR 9191 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150754045
**[Test build #1949 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1949/consoleFull)**
for PR 9191 at commit
Github user viper-kun commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150747910
@davies This test is flaky, pls re-test 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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150341204
This test is flaky, just re-test 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150341971
**[Test build #1941 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1941/consoleFull)**
for PR 9191 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150366058
**[Test build #1941 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1941/consoleFull)**
for PR 9191 at commit
Github user viper-kun commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150176502
Hi @davies,
Sorry, I do not understand Python. Can you help me fix it?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user viper-kun commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150076597
@JoshRosen
In my test environment, it do not have this error. Pls retest it.Thanks!
---
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/9191#issuecomment-150078834
Merged build triggered.
---
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/9191#issuecomment-150078962
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150081227
**[Test build #44118 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44118/consoleFull)**
for PR 9191 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-150097964
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/9191#issuecomment-150097963
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/9191#issuecomment-150097912
**[Test build #44118 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44118/consoleFull)**
for PR 9191 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149850499
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/9191#issuecomment-149850422
**[Test build #44053 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44053/consoleFull)**
for PR 9191 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149850496
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/9191#issuecomment-149804492
**[Test build #44033 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44033/consoleFull)**
for PR 9191 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149804561
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/9191#issuecomment-149804558
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 viper-kun commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149825404
Thanks @JoshRosen
Sorry, I don't do performacne test. As I know, it will reduce number of
open file. When there too much empty file, it will get some
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149825186
Merged build triggered.
---
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/9191#issuecomment-149825211
Merged build started.
---
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 viper-kun opened a pull request:
https://github.com/apache/spark/pull/9191
[SPARK-11225]Prevent generate empty file
If no data will be written into the bucket, it will be generate empty
files. So open() must be called in the first write(key,value).
You can merge
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149769066
Jenkins, this is 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149770096
**[Test build #44033 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44033/consoleFull)**
for PR 9191 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149766373
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9191#issuecomment-149769289
Merged build triggered.
---
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/9191#issuecomment-149769302
Merged build started.
---
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
34 matches
Mail list logo
