You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2015/09/02 15:15:46 UTC
[jira] [Updated] (IGNITE-1358) PortableMarshaller: 'userType' flag
is not written for objects of some types
[ https://issues.apache.org/jira/browse/IGNITE-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-1358:
--------------------------------
Description:
The 'userType' flag is not written when the following classes are serialized:
- enums;
- object and enum arrays;
- classes.
This leads to the situation that the predefined types map is ignored during deserialization and the type is always considered as user's.
To support this feature requires changes in the portable protocol.
For now there is a workaround in the code.
Ideally, the protocol must be changes and the workaround must be removed.
was:
The 'userType' flag is not written when the following classes are serialized:
- enums;
- object and enum arrays;
- classes.
This leads to the situation that the predefined types map is ignored during deserialization and the type is always considered as user's.
To support this feature requires changes in the portable protocol.
For now there is a workaround in the code.
> PortableMarshaller: 'userType' flag is not written for objects of some types
> ----------------------------------------------------------------------------
>
> Key: IGNITE-1358
> URL: https://issues.apache.org/jira/browse/IGNITE-1358
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Magda
> Assignee: Denis Magda
> Priority: Critical
>
> The 'userType' flag is not written when the following classes are serialized:
> - enums;
> - object and enum arrays;
> - classes.
> This leads to the situation that the predefined types map is ignored during deserialization and the type is always considered as user's.
> To support this feature requires changes in the portable protocol.
> For now there is a workaround in the code.
> Ideally, the protocol must be changes and the workaround must be removed.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)