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 2016/06/03 11:18:59 UTC
[jira] [Updated] (IGNITE-3244) Custom arrays are not serialized
properly by CacheObjectBinaryProcessorImpl
[ https://issues.apache.org/jira/browse/IGNITE-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-3244:
--------------------------------
Summary: Custom arrays are not serialized properly by CacheObjectBinaryProcessorImpl (was: Custom arrays are not serialized/deserialized properly by CacheObjectBinaryProcessorImpl)
> 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: Denis Magda
> Priority: Critical
> Fix For: 1.7
>
>
> 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.4#6332)