Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/16165
@markhamstra Thanks all.
btw: what if there are many redundant inprogress files in the disk and
impact the system performance?
---
If your project is set up for it, you can reply to
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16165
@merlintang Marcelo's point remains the same for 2.1.1. We don't typically
backport changes to maintenance branches unless they are fixes for regression
errors or severe bugs.
---
If your
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/16165
@vanzin sorry, I mean the 2.1.1
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/16165
2.1 has already shipped and this is not a regression.
---
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 merlintang commented on the issue:
https://github.com/apache/spark/pull/16165
should we backport this into 2.1? @vanzin
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/16165
Merging 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,
Github user seyfe commented on the issue:
https://github.com/apache/spark/pull/16165
Thank @vanzin. Updated the description based on final state.
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/16165
Code LGTM but can you update the description to reflect the recent changes
to the PR?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69827/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16165
**[Test build #69827 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69827/consoleFull)**
for PR 16165 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16165
**[Test build #69827 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69827/consoleFull)**
for PR 16165 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69809/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16165
**[Test build #69809 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69809/consoleFull)**
for PR 16165 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16165
**[Test build #69809 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69809/consoleFull)**
for PR 16165 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16165
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 feature
enabled and wishes so,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69773/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16165
**[Test build #69773 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69773/consoleFull)**
for PR 16165 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69745/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16165
**[Test build #69745 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69745/consoleFull)**
for PR 16165 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16165
**[Test build #69745 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69745/consoleFull)**
for PR 16165 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16165
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
enabled and wishes so, or if the
25 matches
Mail list logo
