[
https://issues.apache.org/jira/browse/IGNITE-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370629#comment-15370629
]
Denis Magda commented on IGNITE-3455:
-------------------------------------
The issue was in the fact that C++ always gets the type ID from a type name in
the lower case form ignoring BinaryBasicIdMapper settings. Setting the setting
to the following parameter fixed the issue
{code}
<property name="idMapper">
<bean class="org.apache.ignite.binary.BinaryBasicIdMapper">
<property name="lowerCase" value="true"/>
</bean>
</property>
{code}
Igor, please do the following as a part of this ticket:
- update readme.io adding information on how {{BinaryConfiguration}} must be
configured in case of the heterogeneous cluster ;
- add the tests.
> 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)
