Hello! I think you could use MERGE INTO DST SELECT SRC.cols, DST.cols FROM SRC JOIN DST - this way you could fetch proper values for DST columns instead of nullifying. Note that it may have collocation considerations (make sire DST and SRC are collocated).
Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 23:46, vitalys <[email protected]>: > Hi, I have to follow-up. > > MERGE INTO works fine when I define matching fields between SOURCE and > DESTINATION caches. However, Merge command nullifies fields in the > DESTINATION table when they are not part of the SOURCE. > > for Instance an object in cache DST has 3 fields : field1, field2, field3 > with values :1,2,3 > an object in cache SRC also has 3 fields : field2, field3, field4 with > values. > > When I MERGE an object from SRC cache with an Object in DST cache : > > MERGER INTO DST ( field2,field3,_key) > SELECT field2,field3,_key FROM SRC where _key = <somevalue> > > it updates fields : field2, field3 in DST cache to 2 and 3, but it also > updates field1 to NULL. > > How do I preserve an existing values in the Destionation cache. > > I did some research and it seems like MERGE INTO .... WHEN MATCHED ... > construct is not supported by Ignie. > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
