Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-11-01 Thread Vladimir Ozerov
Denis, See my comment in the ticket. It is a problem with scripts, not with engine. On Sat, Oct 28, 2017 at 12:25 AM, Denis Magda wrote: > Vladimir, > > With pleasure, here is a ticker with the reproducer: > https://issues.apache.org/jira/browse/IGNITE-6785 > > — > Denis > > > On Oct 24, 2017,

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-10-27 Thread Denis Magda
Vladimir, With pleasure, here is a ticker with the reproducer: https://issues.apache.org/jira/browse/IGNITE-6785 — Denis > On Oct 24, 2017, at 5:57 AM, Vladimir Ozerov wrote: > > Denis, > > Is it possible to create a test with reproducer? I am a bit lost. > > On Tue, Oct 24, 2017 at 3:12 AM,

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-10-24 Thread Vladimir Ozerov
Denis, Is it possible to create a test with reproducer? I am a bit lost. On Tue, Oct 24, 2017 at 3:12 AM, Dmitriy Setrakyan wrote: > It looks like the case sensitivity for the affinity key is a bug. Vladimir, > what do you think? > > On Mon, Oct 23, 2017 at 11:19 AM, Denis Magda wrote: > > > V

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-10-23 Thread Dmitriy Setrakyan
It looks like the case sensitivity for the affinity key is a bug. Vladimir, what do you think? On Mon, Oct 23, 2017 at 11:19 AM, Denis Magda wrote: > Vladimir, thanks a lot for looking into this! > > > On Oct 23, 2017, at 12:35 AM, Vladimir Ozerov > wrote: > > > > Denis, > > > > Now more detail

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-10-23 Thread Denis Magda
Vladimir, thanks a lot for looking into this! > On Oct 23, 2017, at 12:35 AM, Vladimir Ozerov wrote: > > 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. > Improvem

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-10-23 Thread Vladimir Ozerov
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,

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-10-21 Thread Vladimir Ozerov
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

Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-10-20 Thread Denis Magda
> On Oct 20, 2017, at 3:56 PM, Denis Magda 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

Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-10-20 Thread Denis Magda
Folks, After we added CACHE_NAME, KEY_TYPE and VALUE_TYPE parameters [1] to CREATE TABLE syntax for 2.3, I’ve returned to a simple demo application [2] that aims to show how to use key-value, compute, service grid APIs in the cluster fully configured with DDL. So, what was done and works: * st