Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12189
---
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 ena
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206484912
LGTM. Merging to master. 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206479699
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206479703
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206479498
**[Test build #55123 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55123/consoleFull)**
for PR 12189 at commit
[`e0408f3`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206469514
**[Test build #55123 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55123/consoleFull)**
for PR 12189 at commit
[`e0408f3`](https://gi
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206469324
@holdenk Updated.
@yhuai Changed unpersist(), the `os.unlink()` is moved to destroy()
---
If your project is set up for it, you can reply to this email and have
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206114097
Seems this PR does not change unpersist? Is the behavior of unpersist
correct?
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206049732
Minor point: would it make sense to also update the PyDoc for unpersist to
match the scaladoc while we are fixing its behavior anyways?
---
If your project is set up f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206043600
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206043462
**[Test build #55053 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55053/consoleFull)**
for PR 12189 at commit
[`cdee210`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206043594
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206039488
**[Test build #55053 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55053/consoleFull)**
for PR 12189 at commit
[`cdee210`](https://gi
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/12189
[SPARK-14418] [PYSPARK] fix unpersist of Broadcast in Python
## What changes were proposed in this pull request?
Currently, Broaccast.unpersist() will remove the file of broadcast, which
sh
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12189#issuecomment-206039178
cc @yhuai
---
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
ena
15 matches
Mail list logo
