Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r10551206
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1025,6 +1025,14 @@ abstract class RDD[T: ClassTag](
checkpointData.flatMap(_.getCheckpointFile)
}
+ def cleanup() {
--- End diff --
I think it makes sense to keep cleanup() has a user-visible function rather
than forcing them to rely on finalizers. In general, I suppose cleaning up an
RDD means it is no longer valid to use while unpersisting just means it's no
longer taking up space in the BlockManager. I can see use cases for either.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
