Hello, Slava. > MessageFactory
`MessageFactory` are deprecated and related to Communication SPI which must be reworked for supporting compatibility. So, I think we must clean up this code and remove all deprecated parts before starting. Moreover, current approach when we want to sent each field name to provide compatibility looks ugly, for me. > Ignite Data Transfer Object One more way to send data over the wire - looks like each Ignite contributor invented it's own serdes (sic!). Moreover, serdes code crafted and supported without any code generation. Used in control.sh, mostly therefore must provide compatibility. It seems that we can safely reuse some other serdes approach here and make code a bit easier. > On 2 Dec 2024, at 12:45, Вячеслав Коптилин <slava.kopti...@gmail.com> wrote: > > Hello Nickolay, > > This is a good idea! I fully support it. > > Could you please specify the particular points related to phase 0 (code > cleanup)? > > - MessageFactory. > - IgniteDataTransferObject > > > What should be done with IgniteDataTransferObject and why? > > Thanks, > S. > > пт, 29 нояб. 2024 г. в 18:35, Nikolay Izhikov <nizhi...@apache.org>: > >> Hello, Igniters. >> >> Rolling Upgrade are crucial missing feature for Ignite. >> I propose to implement it. >> >> RU support are complex task and require some well thought out decisions to >> be made. >> Please, take a look at the IEP [1] and share your feedback. >> >> [1] >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-132+Rolling+Upgrade
