Hello! Apache Ignite is an SQL engine on top of key-value, not the vice versa. It means that no SQL statements are fired when you update the underlying key-value. Instead, old and new values are feed to Indexing SPI or its SQL equivalent. see https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/indexing/IndexingSpi.html
Regards, -- Ilya Kasnacheev вс, 2 дек. 2018 г. в 11:35, kcheng.mvp <[email protected]>: > when persistence enabled, when call IgniteCache.put(k,v) with a `NEW` > key-value pair, it's obviously that > there is a new `INSERT` sql generated and the values will be inserted into > the backend table. > > > but for the case when I want to update the properties of the value entity > (eg, the weight property of Dog entity) > > if call via IgniteCache.put(k,v), how the backend Sqls issued ? > 1 : use two sqls: first issue a `DELETE` and then issue a `INSERT`? > 2: use single sql: `UPDATE` including`ALL` properties(columns) > 3: or ignite is smart enough just to update the `CHANGED` > properties(columns) with a single update? > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
