ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3244) Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl
Date Mon, 13 Feb 2017 14:19:41 GMT

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

Alexey Kuznetsov commented on IGNITE-3244:
------------------------------------------

[~vozerov] If you look at CacheObjectContext#unwrapBinary() you will see at the end : co.value(this,
cpy) . Which evaluates unmarshelling 

> Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-3244
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3244
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>            Assignee: Alexey Kuznetsov
>            Priority: Minor
>             Fix For: 2.0
>
>
> If to put a custom object array into a cache like this one
> {code}
>             TestObject[] arr = new TestObject[] {new TestObject(i)};
>             cache.put(0, arr);
> {code}
> then it will be serialized as Object[] array in {{CacheObjectBinaryProcessorImpl.marshallToBinary}}
method.
> This leads to the situation when object's array type is lost and on cache.get the code
below produces {{ClassCastException}}
> {code}
> TestObject[] obj = cache.get(i);
> {code}
> The full test is already added into {{GridCacheBinaryObjectsAbstractSelfTest.testCustomArrays}}.
> To fix the issue we have to revisit logic of {{CacheObjectBinaryProcessorImpl.marshallToBinary}}
and {{CacheObjectContext.unwrapBinary}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message