[
https://issues.apache.org/jira/browse/IGNITE-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370224#comment-15370224
]
Denis Magda commented on IGNITE-3455:
-------------------------------------
[~isapego], know I see what should be going on. Type ID is serialized as a part
of object's byte array. It means that "equals" will fail when we try to get an
object from a Java side because the Java key will have a different type ID in
its serialized byte array.
So seems that there is no issue at all. We have to update our C++ docs showing
what must be defined to avoid such exception in the future.
Also could you add a test that will check the scenario of this ticket (cache is
updated on C++ side and data is retrieved from Java)?
> Entry placed on C++ side is not found on Java side
> --------------------------------------------------
>
> Key: IGNITE-3455
> URL: https://issues.apache.org/jira/browse/IGNITE-3455
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
> Reporter: Denis Magda
> Assignee: Igor Sapego
> Priority: Blocker
> Attachments: cpp.zip, java.zip
>
>
> If a custom key is used for cache values then the following scenario doesn't
> work:
> - value is placed on C++ side;
> - value is read on Java side (value is not found here).
> Reverse direction is not workable as well.
> HashCode is implemented properly in C++ and Java.
> Fast debugging showed that a partition and primary node is calculated
> properly. Looks like that there is a serialization related issue that leads
> to the situation when "equals" fails during an object lookup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
