ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergi Vladykin <sergi.vlady...@gmail.com>
Subject Re: Stable binary key representation
Date Wed, 29 Mar 2017 17:38:26 GMT
It looks like a good idea to drop identity resolvers for now and require
stable binary representation for keys in 2.0. Later if it will be really
needed we will be able to add them back.


2017-03-29 19:08 GMT+03:00 Alexey Goncharuk <alexey.goncharuk@gmail.com>:

> Guys,
> I stumbled across this ticket [1] and it seems to me that the whole
> approach of identity resolvers is error-prone. If a key contains some data
> that does not participate in equals() calculation, these fields may be as
> well moved to the value object. Even with binary objects, key mutation
> looks like an error-prone approach.
> I suggest we remove identity resolver in Ignite 2.0 and ask a user to
> provide a correct implementation of a key. For the Hibernate integration, I
> think a correct fix would be to replace the Hibernate key with another
> correct key class.
> Thoughts?
> [1] https://issues.apache.org/jira/browse/IGNITE-3429

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message