Hello! I hope to see Apache Ignite release 3.0 as API trimming release. Let us correct external and internal APIs for which we have better ideas now, as well as remove old and deprecated code.
We may also introduce new configuration mechanisms and user-facing API (such as cache-less native SQL queries), but this we could prototype before starting the 3.0 task. I will advise against targeting large new features at 3.0. They can be added in subsequent point releases, whereas we can't really remove or remodel stuff in point releases. Regards, -- Ilya Kasnacheev чт, 6 авг. 2020 г. в 03:54, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Igniters, > > I would like to kick off a discussion regarding Ignite 3.0. Ignite 2.0 > exists for more than 3 years now and we've already collected a significant > list [1] of changes that we would like to have, but cannot implement > without breaking compatibility. > > I think it's time to start planning for the next major release and > discussing what should be included. I've already gathered some information > and feedback, and have some thoughts on how to approach this. In the next > few days, I will put everything into a Wiki page and will share it once > this is done. Stay tuned! > > I'm willing to drive the 3.0 activities going forward as well. > > In the meantime, if there are any immediate thoughts or ideas, please feel > free to join the thread and share them. > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist > > Regards, > Val >
