You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr Polovtcev (Jira)" <ji...@apache.org> on 2022/09/27 06:57:00 UTC

[jira] [Resolved] (IGNITE-14817) Custom serializable types

     [ https://issues.apache.org/jira/browse/IGNITE-14817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksandr Polovtcev resolved IGNITE-14817.
------------------------------------------
    Resolution: Won't Fix

Looks like this ticket is no longer needed, since User Object Serialization has been implemented

> Custom serializable types
> -------------------------
>
>                 Key: IGNITE-14817
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14817
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: networking
>            Reporter: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>
> The network component is currently only able to serialize objects that either extend the {{NetworkMesssage}} interface or that belong to a predefined set of types, like strings, primitives and different collections. This is inconvenient, because messages might contain other objects as their properties, which might not extend {{NetworkMessage}}.
> It is proposed to update the current serialization infrastructure to use the new {{@Transferrable}} annotation to generate serialization classes and to decouple it from the {{NetworkMessage}} interface in order to use it for arbitrary objects that satisfy the same contract as the current serializable message do.



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