[
https://issues.apache.org/jira/browse/IGNITE-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225102#comment-16225102
]
Igor Sapego commented on IGNITE-6717:
-------------------------------------
[~dmagda],
I'm not sure what should be added to C++ documentation, as there is no any
standard methods as {{hashCode}} or {{equals}}, so I don't see why should I
mention them. Like "There could be such methods but they are not here" - to me
it looks like this is only going to confuse reader. What do you think?
> Hashcode/equals is not needed for custom keys serialized into a binary form
> ---------------------------------------------------------------------------
>
> Key: IGNITE-6717
> URL: https://issues.apache.org/jira/browse/IGNITE-6717
> Project: Ignite
> Issue Type: Task
> Security Level: Public(Viewable by anyone)
> Components: documentation
> Reporter: Denis Magda
> Assignee: Prachi Garg
> Fix For: 2.3
>
>
> It turns out that hashCode/equals implementation is no longer required for
> custom complex keys if a key is serialized to the binary form. Discussed here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-3-troubles-with-key-value-APIs-in-the-cluster-configured-with-DDL-td23501.html#a23506
> The marshaller calculates the hash code automatically. This info has to be
> added to the binary marshaller page:
> https://apacheignite.readme.io/docs/binary-marshaller
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
