Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/1082#issuecomment-50369852
The simple case I had in mind was a user finished exploring one set of
transformations in shell and wanted to free all the memory before starting the
next set. I admit this is a narrow use case and the method is merely a
convenience for not having to remember persisted RDDs.
Your persistence context idea is certainly worth exploring. Maybe it should
be tied to job group -- a call will unpersist all the RDDs created by a job
group?
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
