>> * Twitter module Every extension/adapter/etc module should be checked to be useful. My wish is to get rid of all lesser-used features, to make AI as small as possible. It's time to clean-up legacy :)
BTW, do we really need TCK support? On Mon, Jun 17, 2019 at 4:05 PM Andrey Mashenkov <andrey.mashen...@gmail.com> wrote: > Alexey, > > * SqlQuery (not SqlFieldsQuery) > * Twitter module > > On Mon, Jun 17, 2019 at 3:52 PM Alexey Goncharuk < > alexey.goncha...@gmail.com> > wrote: > > > Nikolay, > > > > Local caches and scalar are already in the list :) Added the outdated > > metrics point. > > > > пн, 17 июн. 2019 г. в 15:32, Nikolay Izhikov <nizhi...@apache.org>: > > > > > * Scalar. > > > * LOCAL caches. > > > * Deprecated metrics. > > > > > > В Пн, 17/06/2019 в 15:18 +0300, Alexey Goncharuk пишет: > > > > Igniters, > > > > > > > > Even though we are still planning the Ignite 2.8 release, I would > like > > to > > > > kick-off a discussion related to Ignite 3.0, because the efforts for > AI > > > 3.0 > > > > will be significantly larger than for AI 2.8, better to start early. > > > > > > > > As a first step, I would like to discuss the list of things to be > > removed > > > > in Ignite 3.0 (partially this thread is inspired by Denis Magda's > IGFS > > > > removal thread). I've separated all to-be-removed points from > existing > > > > Ignite 3.0 wishlist [1] to a dedicated block and also added a few > more > > > > things that look right to be dropped. > > > > > > > > Please share your thoughts, probably, there are more outdated things > we > > > > need to add to the wishlist. > > > > > > > > As a side question: I think it makes sense to create tickets for such > > > > improvements, how do we track them. Will the 3.0 version suffice or > > > should > > > > we add a separate label? > > > > > > > > -- > Best regards, > Andrey V. Mashenkov >
