[jira] [Created] (IGNITE-6698) Document CREATE TABLE "DATA_REGION" option

Vladimir Ozerov created IGNITE-6698: --- Summary: Document CREATE TABLE "DATA_REGION" option Key: IGNITE-6698 URL: https://issues.apache.org/jira/browse/IGNITE-6698 Project: Ignite Issue

[jira] [Created] (IGNITE-6697) Invalid cluster state after attempt to create a cache with invalid data region

Vladimir Ozerov created IGNITE-6697: --- Summary: Invalid cluster state after attempt to create a cache with invalid data region Key: IGNITE-6697 URL: https://issues.apache.org/jira/browse/IGNITE-6697

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

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

> 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

Re: Client Near Cache Configuration Lost after Cluster Node Removed

+ user list > On Oct 20, 2017, at 11:00 PM, Denis Magda wrote: > > Ignite caching experts please chime in. > >> Begin forwarded message: >> >> From: torjt >> Subject: Client Near Cache Configuration Lost after Cluster Node Removed >> Date: October

Fwd: Client Near Cache Configuration Lost after Cluster Node Removed

Ignite caching experts please chime in. > Begin forwarded message: > > From: torjt > Subject: Client Near Cache Configuration Lost after Cluster Node Removed > Date: October 16, 2017 at 2:54:08 PM PDT > To: u...@ignite.apache.org > Reply-To: u...@ignite.apache.org > >