You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2017/10/23 18:11:00 UTC

[jira] [Updated] (IGNITE-6717) Hashcode/equals is not needed for custom keys serialized into a binary form

     [ https://issues.apache.org/jira/browse/IGNITE-6717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Magda updated IGNITE-6717:
--------------------------------
    Component/s: documentation

> 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: Denis Magda
>             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)