You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/04/07 11:28:41 UTC

[jira] [Commented] (IGNITE-4889) Replacement of Cache Key classes with fields not participating in equals operation

    [ https://issues.apache.org/jira/browse/IGNITE-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960626#comment-15960626 ] 

Alexey Goncharuk commented on IGNITE-4889:
------------------------------------------

Merged in ignite-3477-master. Will be merged to master after all tests are fixed.

> Replacement of Cache Key classes with fields not participating in equals operation
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-4889
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4889
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Sergey Chugunov
>            Assignee: Dmitriy Govorukhin
>             Fix For: 2.0
>
>
> h2. Notes
> Having key classes with fields not participating in *equals* operation leads to errors when handling them in B+Tree data structures.
> It is discussed here in more details: [dev-list discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Stable-binary-key-representation-td15904.html]
> h2. Acceptance Criteria
> # All classes known to have such flaw are replaced at run time to use them safely within B+Tree.
> # All tests marked with this issue number are passing.
> h2. Out-of-scope
> *BinaryIdentityResolver* approach is deprecated when solution described above is implemented and proven to be working.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)