Hello! As far as my understanding goes, MERGE INTO is not optimized, this means it will try to lock key (a subset of table data even) before writing to table and maybe hold them all until batch is finished.
Using MERGE INTO were discouraged by Ignite SQL developers last time I have asked. It exists mostly as legacy from H2. Regards, -- Ilya Kasnacheev вт, 30 окт. 2018 г. в 14:20, yangjiajun <1371549...@qq.com>: > Hi,I do a test to verify write performance of ignite.My test data set has > 6000 records.Each record has 10 columns.It takes 160 seconds to batch write > into Ignite table using "merge into" command while it only takes 3 seconds > when use "insert into" command.Why merge into statement is so slow? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
