Denis, Nikolai, Suppose, issue IGNITE-7165 [1] is already included in the release scope, but I think I can mention it here.
It's about re-balance optimization - now client node join\left doesn't affect re-balance process. In general, it's not so much about client node as about if assignments not change re-balance will not be interrupted. I've provided all implementation details in JIRA comment [2]. Hope it will help someone with further optimizations. [1] https://issues.apache.org/jira/browse/IGNITE-7165 [2] https://issues.apache.org/jira/browse/IGNITE-7165?focusedCommentId=16561092&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16561092 On Wed, 29 Aug 2018 at 02:43 Denis Magda <dma...@apache.org> wrote: > Nikolay, Igniters, let me help you with the list. > > That what I was tracking on my side (something we can announce). Don't have > a JIRA ticket for every ticket but CC-ed everyone who claimed to be in > charge. Nikolay, please work with the community members to add these > capabilities to the release wiki page. If something doesn't get delivered > then let's exclude it. > > 1. Partition map exchange optimizations. Are we releasing any of them? > *(Sergey > Chugunov, Andrey Mashenkov)* > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-25%3A+Partition+Map+Exchange+hangs+resolving > > 2. Java 9/10/11 Support. Are we on track to support it better? *(Peter, > Vladimir)*. > > 3. SQL *(Vladimir)*: > > - Transactional SQL beta? > - Basic monitoring facilities (inline index alerts, page reads/writes > per type)? > - SQL index update optimizations? ( > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-19%3A+SQL+index+update+optimizations > ) > - ODBC/JDBC session management > - Result set offload to disk. Looks it doesn't get to the release? > https://issues.apache.org/jira/browse/IGNITE-7526 > > 4. JCache 1.1 support. Completed! > > 5. Transparent data encryption? What exactly goes in 2.7? *(Nikolay)*. > > 6. Ignite + Informatica integration > > 7. Ignite and Spring Session integration (heard it was done but the ticket > is still Open): > https://issues.apache.org/jira/browse/IGNITE-2741 > > 8. Service Grid 2.0. What exactly goes in 2.7? (*Vyacheslav)* > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-17%3A+Oil+Change+in+Service+Grid > > 9. Ignite Multi Map *(Amir, Anton)* > https://issues.apache.org/jira/browse/IGNITE-640 > > 10. Thin Clients: > > - Node.JS (https://issues.apache.org/jira/browse/IGNITE-7777) - *Pavel > Petroshenko* > - Python (https://issues.apache.org/jira/browse/IGNITE-7782) - *Pavel > Petroshenko, **Dmitry Melnichuk* > - PHP (https://issues.apache.org/jira/browse/IGNITE-7783) - *Pavel P., > Ekaterina* > - C++: *Igor S.* > - Affinity awareness for thin clients (*Igor S.*): > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients > > 11. Machine and Deep Learning (preprocessing APIs, TensorFlow integration, > extra algorithms) - *Yuri and our ML experts* > > > > On Tue, Aug 28, 2018 at 10:17 AM Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > Hi Nikolai, > > > > Generally looks OK, however, It is hard to comment on your schedule > without > > seeing a full list of all must-have features we plan to add to this > > release. I am hoping that the community will see this list at some point. > > > > D. > > > > On Tue, Aug 28, 2018 at 8:23 AM, Nikolay Izhikov <nizhi...@apache.org> > > wrote: > > > > > Hello, Igniters. > > > > > > I think we should discuss the release schedule. > > > > > > Current dates are following: > > > > > > * Code Freeze: September 30, 2018 > > > * Voting Date: October 1, 2018 > > > * Release Date: October 15, 2018 > > > > > > We discussed it privately with Vladimir Ozerov. > > > > > > Is seems better to reschedule a bit: > > > > > > * Scope freeze - September 17 - We should have a full list of > > > tickets for 2.7 here. > > > * Code freeze - October 01 - We should merge all 2.7 tickets to > > > master here. > > > * Vote - October 08. > > > > > > What do you think? > > > > > > > > > В Сб, 25/08/2018 в 00:57 +0300, Dmitriy Pavlov пишет: > > > > I hope Vyacheslav can comment better than me. I suppose it is, more > or > > > > less, rectifications and clarifications of design aspects. Not > overall > > > > redesign. > > > > > > > > I also hope Igniters, especially Services experts, will join the > > > discussion > > > > in the separate topic. Now after a couple of days there is no > reaction. > > > > > > > > сб, 25 авг. 2018 г. в 0:53, Dmitriy Setrakyan <dsetrak...@apache.org > >: > > > > > > > > > On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov < > > dpavlov....@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > Hi Dmitriy, I suppose it highly depends on how fast community > will > > > come > > > > > > > > > > to > > > > > > a consensus about design. So it is up to us to make this happen > > > > > > > > > > > > > > > > I am confused then. If we are still discussing design, then we are > > > miles > > > > > away. Do you know if there anything in service grid that has > already > > > been > > > > > implemented and can be released? > > > > > > > > > > > -- -- Maxim Muzafarov
