Description
Currently if there is no configured BinaryTypeConfiguration.IdentityResolver, we call Object.hashCode().
This is not consistent with DML, and there is a warning:
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.
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
Attachments
Issue Links
- Blocked
-
IGNITE-4869 Unnecessary benchmarks for legacy binary identity
- Resolved
- Is contained by
-
IGNITE-4547 Apache Ignite 2.0 quick and needed tasks
- Resolved
- is related to
-
IGNITE-4351 .NET: Use BinaryArrayIdentityResolver by default
- Resolved
- relates to
-
IGNITE-7881 Add tests for using TreeMap/TreeSet in cache key
- Resolved
-
IGNITE-4215 Introduce global identity resolver for binary objects.
- Closed