Denis, Now more detailed answer:
1) It is expected that "City" class is not be found. You should set key/value type names to fully-qualified class name to make it work. Improvements: docs 2) There is no need to implement hash code. Why did you do this? 3) We will not have case-insensitive policy, SQL databases doesn't work this way. In order to preserve case you should define column name in quotes. On Sat, Oct 21, 2017 at 2:34 PM, Vladimir Ozerov <voze...@gridgain.com> wrote: > 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 <dma...@apache.org>: > >> >> > On Oct 20, 2017, at 3:56 PM, Denis Magda <dma...@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 > >
