Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-43039785
> How can you make sure that in future versions of PySpark, the same
deserializer will be used?
@mateiz Obviously we can't. I started with forcing the pickle serializer
but dismissed it since 1) we can't promise we won't change it down the road and
2) users may want to use a different serializer for object file. So I kind of
felt saveAsObjectFile was only suitable for temporary persistence, hence
settled on using the default serializer. Now that you suggested naming the
methods saveAsPickleFile and pickleFile, it makes forcing pickle serializer
much more natural. The user still has to remember which method he/she called to
save to file though. Will update.
---
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.
---
