[
https://issues.apache.org/jira/browse/ARROW-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292068#comment-16292068
]
ASF GitHub Bot commented on ARROW-1924:
---------------------------------------
pcmoritz commented on issue #1420: ARROW-1924: [Python] Bring back pickle=True
option for serialization
URL: https://github.com/apache/arrow/pull/1420#issuecomment-351920239
+1, the windows test failure is unrelated I think
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [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
>
> 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)
