Hi Rick. Actually, if you do not need to use your POJO classes on the server-side (e.g. for some compute tasks or in services) you can try just enabling peerClassLoding and put a new object from your client without any interruption. In this case, Ignite will serialize a new object and create in the cluster metadata a new schema for your POJO-type. The best way is a monotonic expansion of object fields set.
------------------ Ilya ср, 27 окт. 2021 г. в 09:34, Rick Lee <eerick...@gmail.com>: > Dear all, > > I'm currently on version 2.8 and use ignite.getOrCreateCache(cacheCfg) to > create a cache, e.g., cache Account object, etc, on startup. Now whenever I > want to add field to the Account class, I need to restart all nodes in the > cluster in order to make the change effective, but obviously it will > introduce service interruption. Any other way I can modify the class > structure by only rolling restart the nodes instead of restarting the whole > cluster? > > Thanks & Regards, > Rick >
