ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: Stable binary key representation
Date Wed, 29 Mar 2017 18:43:00 GMT
"Hibernate key" is the CacheKey class I was referring to. It's provided by
Hibernate, not by user and not by us. So I'm not sure it's possible to
replace it.

-Val

On Wed, Mar 29, 2017 at 11:36 AM, Dmitriy Setrakyan <dsetrakyan@apache.org>
wrote:

> Alexey,
>
> Can you explain what is the "Hibernate key" and what is a "correct key
> class"? Are you suggesting that currently we don't require our users
> interested in Hibernate integration to provide a "correct key class"?
>
> D.
>
> On Wed, Mar 29, 2017 at 9:08 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
> > 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
> >
>

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