[
https://issues.apache.org/jira/browse/IGNITE-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PetrovMikhail updated IGNITE-10396:
-----------------------------------
Description:
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.
was: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.
Summary: Serialization issue of class with HashMap field (was:
IgniteCache Key class with HashMap field doesn't recognized in some cases)
> Serialization issue of class with HashMap field
> -----------------------------------------------
>
> Key: IGNITE-10396
> URL: https://issues.apache.org/jira/browse/IGNITE-10396
> Project: Ignite
> Issue Type: Bug
> Environment: [^IgniteCacheRemoveTest.java]
> Reporter: PetrovMikhail
> Priority: Major
> Attachments: IgniteCacheRemoveTest.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
(v7.6.3#76005)
