[
https://issues.apache.org/jira/browse/IGNITE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973399#comment-15973399
]
Denis Magda commented on IGNITE-3429:
-------------------------------------
Binary resolvers based workaround is no longer applicable for 2.0. The issue
has to be fixed differently. See the discussion:
http://apache-ignite-developers.2346864.n4.nabble.com/Stable-binary-key-representation-td15904.html
> org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
> -----------------------------------------------------------------------------
>
> Key: IGNITE-3429
> URL: https://issues.apache.org/jira/browse/IGNITE-3429
> Project: Ignite
> Issue Type: Sub-task
> Components: cache, Hibernate L2 cache
> Affects Versions: 1.6
> Reporter: Valentin Kulichenko
> Assignee: Andrew Mashenkov
> Priority: Blocker
> Fix For: 2.0
>
>
> {{org.hibernate.cache.spi.CacheKey}} is a class used as a key for all entries
> in the Hibernate L2 cache. This class contains {{type}} field and custom
> {{equals}} logic where the type is used as a helper and does not participate
> in comparison. Instances of the same type are producing different hash codes
> in different JVMs, which actually breaks comparison when binary format is
> used, where byte arrays are compared.
> The issue is described in more detail here:
> http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
