[
https://issues.apache.org/jira/browse/ARROW-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney resolved ARROW-1924.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.9.0
Issue resolved by pull request 1420
[https://github.com/apache/arrow/pull/1420]
> [Python] Bring back pickle=True option for serialization
> --------------------------------------------------------
>
> Key: ARROW-1924
> URL: https://issues.apache.org/jira/browse/ARROW-1924
> Project: Apache Arrow
> Issue Type: Bug
> Reporter: Philipp Moritz
> Labels: pull-request-available
> Fix For: 0.9.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
