ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL
Date Sat, 21 Oct 2017 11:34:22 GMT
Denis,

SQL <-> key-Val transparency is complex thing, especially if you work with
real Java classes instead of binary objects.

We will try to improve something in 2.4, but do not expect great usability
here. There is always be some pain in such scenarios.

сб, 21 окт. 2017 г. в 9:23, Denis Magda <dmagda@apache.org>:

>
> > On Oct 20, 2017, at 3:56 PM, Denis Magda <dmagda@apache.org> wrote:
> >
> > * failed to deserialize BinaryObject value to City type [7]. Just
> classical "class org.apache.ignite.binary.BinaryInvalidTypeException: City"
> caused by "Caused by: java.lang.ClassNotFoundException: City”.
>
>
> Recalled that this should be caused by the fact that all the data was
> inserted with DML (cache.put(key, BinaryObjects)) and there was no single
> cache.put(key, new City()) that would register City class. Guess we need to
> add an API that forces classes registration from the app side or something
> more efficient.
>
> —
> Denis

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