ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evgenii Zhuravlev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4558) Use BinaryArrayIdentityResolver by default
Date Fri, 24 Mar 2017 07:26:42 GMT

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

Evgenii Zhuravlev commented on IGNITE-4558:

Review link: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-132, tc link: http://ci.ignite.apache.org/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F1649%2Fhead,
PR link: https://github.com/apache/ignite/pull/1649 

> Use BinaryArrayIdentityResolver by default
> ------------------------------------------
>                 Key: IGNITE-4558
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4558
>             Project: Ignite
>          Issue Type: Improvement
>          Components: binary
>            Reporter: Pavel Tupitsyn
>            Assignee: Evgenii Zhuravlev
>            Priority: Critical
>             Fix For: 2.0
> Currently if there is no configured {{BinaryTypeConfiguration.IdentityResolver}}, we
call Object.hashCode().
> This is not consistent with DML, and there is a warning:
> {code}
> Binary object's type does not have identity resolver explicitly set, therefore BinaryArrayIdentityResolver
is used to generate hash codes for its instances, and therefore hash code of this binary object
will most likely not match that of its non serialized form. For finer control over identity
of this type, please update your BinaryConfiguration accordingly.
> {code}
> In 2.0 we should use {{BinaryArrayIdentityResolver}} by default.
> 2.0 migration guide has to be updated if needed: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide

This message was sent by Atlassian JIRA

View raw message