You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Rok Mihevc (Jira)" <ji...@apache.org> on 2023/01/11 07:15:03 UTC

[jira] [Commented] (ARROW-1418) [Python] Introduce SerializationContext to register custom serialization callbacks

    [ https://issues.apache.org/jira/browse/ARROW-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17658452#comment-17658452 ] 

Rok Mihevc commented on ARROW-1418:
-----------------------------------

This issue has been migrated to [issue #17443|https://github.com/apache/arrow/issues/17443] on GitHub. Please see the [migration documentation|https://github.com/apache/arrow/issues/14542] for further details.

> [Python] Introduce SerializationContext to register custom serialization callbacks
> ----------------------------------------------------------------------------------
>
>                 Key: ARROW-1418
>                 URL: https://issues.apache.org/jira/browse/ARROW-1418
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Python
>    Affects Versions: 0.6.0
>            Reporter: Philipp Moritz
>            Assignee: Philipp Moritz
>            Priority: Minor
>             Fix For: 0.7.0
>
>
> In the first iteration of the Python serialization code, we used global variables to store the custom serialization and deserialization callback functions. This global state is undesirable because if the user wants to use different serialization callbacks with different types registered, they need to remember resetting the state. As Wes suggested, a good way to address this is by introducing a SerializationContext that has the callbacks and gets passed around.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)