Re: write-through when using SQL updates

Kind of this task was planned some time ago. In addition to what you're putting out, users are asking for an example that shows how to blend key-value and SQL APIs. I already have that example. Hopefully, we'll find resources to get it done soon: IGNITE-7728

Re: write-through when using SQL updates

On Sun, Apr 22, 2018 at 10:16 PM, Denis Magda wrote: > 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

Re: write-through when using SQL updates

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 busin

Re: write-through when using SQL updates

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 wrote: > Dmitriy,

Re: write-through when using SQL updates

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-descriptio

write-through when using SQL updates

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.