If a table is created with CREATE TABLE command then: - Ignite creates two custom binary types (one for the key and one for the value) the columns will be wrapped into. A primary key defines what goes into the key. It happens automatically unless... - You define names of existing business objects the columns will be mapped to. Use KEY_TYPE and VALUE_TYPE parameters for that.
Read more here: https://apacheignite-sql.readme.io/docs/create-table#section-description -- Denis On Sun, Apr 22, 2018 at 9:58 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Denis, I get that we support it, but I still do not understand how. Given > an SQL table in Ignite with several columns, what is the key class and what > is the value class? Where do we document how SQL types map to key-value > types? > > D. > > On Sun, Apr 22, 2018 at 1:43 PM, Denis Magda <dma...@apache.org> wrote: > > > Dmitriy, > > > > According to the docs, INSERTS are transformed into cache.putIfAbsent or > > cache.invokeAll operations: > > https://apacheignite-sql.readme.io/docs/insert#section-description > > > > UPDATES are turned into cache.invokeAll all the times: > > https://apacheignite-sql.readme.io/docs/update#section-description > > > > Once an SQL statement becomes a key-value operation(s) we should update > > both RAM and a 3rd party database following a standard contract: > > https://apacheignite.readme.io/docs/3rd-party-store > > > > SQL experts, please confirm my understanding is correct. > > > > -- > > Denis > > > > > > On Sun, Apr 22, 2018 at 7:54 AM, Dmitriy Setrakyan < > dsetrak...@apache.org> > > wrote: > > > > > Igniters, > > > > > > Do we support write-through to a 3rd party database when performing SQL > > > inserts and updates? If yes, how does the mapping between SQL and > > > CacheStore key-value API happen? > > > > > > D. > > > > > >
