Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13181
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220704424
I'm going to go ahead and merge this, but please to ping me on follow up
issues that try to add this back.
---
If your project is set up for it, you can reply to
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220527118
@jurriaan Maybe I am doing this wrong. I will tell you after testing that.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jurriaan commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220526725
Interesting, I'm currently working with a custom build where I've reverted
the PR manually to work around the issue. Will add an testcase to the JIRA
---
If your
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220522607
@marmbrus I tested and could produce the exceptions for reading in
https://issues.apache.org/jira/browse/SPARK-15393 but it seems this might not
be the reason.
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220222603
Hi @marmbrus , it seems okay!
---
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/13181#issuecomment-220207800
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/13181#issuecomment-220207798
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/13181#issuecomment-220207650
**[Test build #58829 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58829/consoleFull)**
for PR 13181 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220200736
@marmbrus Sure 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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220198280
hmmm, this might be failing tests? @HyukjinKwon can you investigate if it
fails again?
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220196004
**[Test build #58829 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58829/consoleFull)**
for PR 13181 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220195260
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220195134
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/13181#issuecomment-220195138
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/13181#issuecomment-220195031
**[Test build #58821 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58821/consoleFull)**
for PR 13181 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220183568
**[Test build #58821 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58821/consoleFull)**
for PR 13181 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220183153
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220180441
**[Test build #58818 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58818/consoleFull)**
for PR 13181 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13181#issuecomment-220180461
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/13181#issuecomment-220180463
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/13181#issuecomment-220179010
**[Test build #58818 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58818/consoleFull)**
for PR 13181 at commit
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/13181
Revert "[SPARK-10216][SQL] Avoid creating empty files during overwritâ¦
This reverts commit 8d05a7a from #8411, which seems to have caused
regressions when working with empty DataFrames.
You
23 matches
Mail list logo
