[
https://issues.apache.org/jira/browse/IGNITE-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-4558:
--------------------------------
Description:
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
was:
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.
> 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
> 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
(v6.3.4#6332)
