Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
We need to revert https://issues.apache.org/jira/browse/ARROW-1758
The reason is that the semantics for pickle=True is slightly different from just using (cloud-)pickle as the custom serializer:
If pickle=True is used, the object can be deserialized in any process, even if a deserializer for that type_id has not been registered in that process. On the other hand, if (cloud-)pickle is used as a custom serializer, the object can only be deserialized if pyarrow has the type_id registered and can call the deserializer.
Attachments
Issue Links
- links to