Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16134
Sure, let me submit a PR to backport it to Spark 2.x branches.
---
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
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/16134
This patch is related to the path #15819 for spark 1.6. In the #15819, I
can add the code from this patch(#16134) now, then we can fix the staging
files issues in the spark 1.6.x.
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16134
sounds good to backport into 2.x branches. We can also backport into 1.6 if
it is easy.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/16134
+1 backport to spark 1.6.x
On Thu, Dec 15, 2016 at 8:14 AM, Xiao Li wrote:
> The staging directory and files will not be removed when users hitting
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16134
The staging directory and files will not be removed when users hitting
abnormal termination of JVM. In addition, if the JVM does not stop, these
temporary files could still consume a lot of
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16134
merging it to master! let's decide if we wanna backport it or not later.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16134
shall we backport this to 2.1/2.0? #16104 was not backported
---
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 issue:
https://github.com/apache/spark/pull/16134
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70133/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16134
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #70133 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70133/consoleFull)**
for PR 16134 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #70133 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70133/consoleFull)**
for PR 16134 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16134
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70128/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16134
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #70128 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70128/consoleFull)**
for PR 16134 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #70128 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70128/consoleFull)**
for PR 16134 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16134
Yeah, let me update it now. 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 this feature
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16134
#16104 merged, can you update it? 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 this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16134
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/16134
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69970/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #69970 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69970/consoleFull)**
for PR 16134 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #69970 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69970/consoleFull)**
for PR 16134 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16134
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/16134
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69641/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #69641 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69641/consoleFull)**
for PR 16134 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #69641 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69641/consoleFull)**
for PR 16134 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16134
https://github.com/apache/spark/pull/15819 is copying the code from Spark
2.0. The file deletion is based on the existing way: `fs.deleteOnExit`. This PR
tries to delete the staging directory
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16134
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69633/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16134
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #69633 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69633/consoleFull)**
for PR 16134 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16134
is this PR related to https://github.com/apache/spark/pull/15819?
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16134
**[Test build #69633 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69633/consoleFull)**
for PR 16134 at commit
31 matches
Mail list logo