Github user uncleGen closed the pull request at:
https://github.com/apache/spark/pull/2488
---
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 en
Github user uncleGen commented on the pull request:
https://github.com/apache/spark/pull/2488#issuecomment-56505578
@pwendell ah, make sense, I will close this PR. Thank you!
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/2488#issuecomment-56446727
On this one, I would prefer the current approach of failing loudly rather
than to silently continue. Existing users might also be depending on this
behavior (e.g. they g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2488#issuecomment-56357881
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20652/consoleFull)
for PR 2488 at commit
[`0e3831c`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2488#issuecomment-56351578
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20652/consoleFull)
for PR 2488 at commit
[`0e3831c`](https://github.com/ap
GitHub user uncleGen opened a pull request:
https://github.com/apache/spark/pull/2488
[SPARK-3636][CORE]:It is not friendly to interrupt a Job when user passe...
... different storageLevels to a RDD
You can merge this pull request into a Git repository by running:
$ git pull ht