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

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/10 11:15:00 UTC

[jira] [Updated] (IGNITE-10396) Serialization issue of class with HashMap field

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

Maxim Muzafarov updated IGNITE-10396:
-------------------------------------
    Fix Version/s:     (was: 2.8)

> Serialization issue of class with HashMap field
> -----------------------------------------------
>
>                 Key: IGNITE-10396
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10396
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: PetrovMikhail
>            Assignee: Dmitriy Govorukhin
>            Priority: Major
>         Attachments: SerializationTest.java
>
>
> If class which cointains HashMap field be serialized to BinaryObject, deserialized and serialized again, hash codes of first and second BinaryObjects will be different.
> That can case the following situation.
> IgniteCache#containsKey or IgniteCache#remove methods return false when in their parameters passed instance of key class produced via cache iterator. Even in so situation when IgniteCache.Entry with such key is existing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)