Igniters, here is curernt status of platform/portable tickets. As I understand, IGNITE-950 is almost ready and will be merged very soon. There are 5 more tickets which depends on it:
*IGNITE-1845*, *IGNITE-1846* - move portable API changes to .Net and C++. This is a matter of refacotring, should not be a problem. *IGNITE-1819* - remove "metadata enabled" flag. Also fairly simple ticket. *IGNITE-1847* - move "field" method from PortableObject to PortableMetadata. Also should be trivial. *IGNITE-1816* - optionaly do not write field IDs to footer. Important ticket, I'm working on it. About ~50% ready. All in all, none of these tickets are showstoppers for merge of IGNITE-950/IGNITE-1282 to release branch. Also I measured query performance on some local benchmarks and got acceptable resutls - queries are about 5-7% slower with poratbles than with OptimizedMarshaller. Looks very promising to me provided that we work with deserialized objects now. On Wed, Nov 4, 2015 at 1:50 AM, Alexey Kuznetsov <akuznet...@gridgain.com> wrote: > I'm working on IGNITE-1753 Rework CacheJdbcPojoStore to new API ( > https://issues.apache.org/jira/browse/IGNITE-1753). > Issue is implemented and waiting for IGNITE-950 to be merged into > ignite-1282. > > On Wed, Nov 4, 2015 at 5:22 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com > > wrote: > > > Good news for the IGNITE-950 ticket - CI looks good, changes will be > merged > > to ignite-1282 integration branch after benchmarks re-run. > > > > 2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <ntikho...@gridgain.com>: > > > > > I implemented changes related to IGNITE-426 task. Currently > investigating > > > performance degradation for atomic caches. I expect the ticket to be > > merged > > > in 2 days. > > > > > > On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk < > > > alexey.goncha...@gmail.com > > > > wrote: > > > > > > > IGNITE-950 is taking more time to be merged than I originally > > estimated. > > > We > > > > had a couple of silly bugs, such as loosing cache operation context > on > > > > async cache operations, which led to hard-to debug failures in the > > > platform > > > > integration code. > > > > I also added some sanity checks to indexing and found that I ran > > > benchmarks > > > > for new binary format on a model with externalizable classes, so the > > > result > > > > I've got were invalid, need more time to fix the model and re-run > > > > benchmarks. > > > > > > > > I am currently waiting for another CI run, will give an update in > > several > > > > hours. > > > > > > > > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <voze...@gridgain.com>: > > > > > > > > > Here are my current status for all interop-related stuff (you can > > view > > > > > these tickets using query "project = IGNITE AND status in (Open, > "In > > > > > Progress", Reopened, Resolved, "Patch Available") AND component = > > > interop > > > > > AND fixVersion = 1.5"): > > > > > > > > > > *IGNITE-1819 - Remove metadataEnabled flag in Java* > > > > > Trivial. Waiting for IGNITE-950 merge. > > > > > > > > > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net* > > > > > Trivial. Waiting for IGNITE-950 merge. > > > > > > > > > > *IGNITE-1803 - Optimized field lookup for queries* > > > > > Ready. Waiting for IGNITE-950 to merge. > > > > > > > > > > *IGNITE-1847 - Add "field" method to portable metadata.* > > > > > Not started yet. Waiting for IGNITE-950 to merge. > > > > > > > > > > *IGNITE-1816 - Optionally do not write field IDs to portable object > > > > > footer.* > > > > > Not started yet. > > > > > > > > > > + Several minor tickets. > > > > > > > > > > All in all, I expect all these tickets to be ready in 2 days. > > > > > > > > > > > > > > > > > > > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk < > > > > > alexey.goncha...@gmail.com > > > > > > wrote: > > > > > > > > > > > I'm sorry, I meant to write "changes related to IGNITE-1486 > > > *ticket*". > > > > > The > > > > > > changes are in ignite-950-new branch because it is a result of > work > > > on > > > > > > multiple sub-tickets and it is currently used as an integration > > > branch. > > > > > > > > > > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan < > dsetrak...@apache.org > > >: > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > I am confused. Why do you have 2 branches? > > > > > > > > > > > > > > D. > > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk < > > > > > > > alexey.goncha...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > > > > I am finalizing changes related to IGNITE-1486 branch. > > Currently > > > > the > > > > > > API > > > > > > > > changes are finished and now I am mostly fixing the CI tests. > > In > > > > > fact, > > > > > > I > > > > > > > > just submitted the latest fix related to the new .NET > platform > > > > > > > > functionality and hope CI tests will pass, in this case it > will > > > be > > > > > > ready > > > > > > > to > > > > > > > > be merged tomorrow morning. > > > > > > > > It would be nice if other community members reviewed my > changes > > > in > > > > > > > > ignite-950-new branch before it gets to master. > > > > > > > > > > > > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan < > > > > dsetrak...@apache.org > > > > > >: > > > > > > > > > > > > > > > > > Thanks Vladislav! > > > > > > > > > > > > > > > > > > Would also be nice to get an update from other committers > > > > involved > > > > > in > > > > > > > the > > > > > > > > > outlined tickets. Specifically whether the ticket has been > > > merged > > > > > to > > > > > > > > master > > > > > > > > > or not, and if not, what should be the expectation. > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > D. > > > > > > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic < > > > > > > > > vladis...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > >10. I would also like to include distributed Semaphore. > > > > > Vladislav, > > > > > > > any > > > > > > > > > > >chance you can finish with it this week? > > > > > > > > > > >https://issues.apache.org/jira/browse/IGNITE- > > > > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638 > > > > > > > > > > > > > > > > > > > > I will have it done by thursday. > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > Vladisav > > > > > > > > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan < > > > > > > > > dsetrak...@apache.org > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G < > endian...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Can/will this include > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681 > > > > > > > > > > > ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I don’t see why not. Would be nice if one of the > > committers > > > > > could > > > > > > > > pick > > > > > > > > > up > > > > > > > > > > > the review for this patch. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov < > > > > > > > > > > > avinogra...@gridgain.com > > > > > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Branch ignite-1.5 created. > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov < > > > > > > > > > > > > avinogra...@gridgain.com > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > I assume that correct link at 10th feature is > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638 > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov < > > > > > > > > > yzhda...@apache.org > > > > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > >> Guys, > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> I think we can start preparation to Ignite-1.5 > > > release > > > > > > which > > > > > > > > > will > > > > > > > > > > > > > include > > > > > > > > > > > > > >> many interesting features: > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 1. Portable object API > > > > > > > > > > > > > >> > https://issues.apache.org/jira/browse/IGNITE-1486 > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 2. Ignite.NET and Ignite C++ > > > > > > > > > > > > > >> > https://issues.apache.org/jira/browse/IGNITE-1282 > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 3. Optimistic serializable transactions > > > > > > > > > > > > > >> > https://issues.apache.org/jira/browse/IGNITE-1607 > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to > > query > > > > > > > > > non-collocated > > > > > > > > > > > > data > > > > > > > > > > > > > as > > > > > > > > > > > > > >> well > > > > > > > > > > > > > >> > https://issues.apache.org/jira/browse/IGNITE-1232 > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability > > > > > > > > > > > > > >> > https://issues.apache.org/jira/browse/IGNITE-1526 > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 6. MQTT streamer > > > > > > > > > > > > > >> > https://issues.apache.org/jira/browse/IGNITE-535 > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 7. Continuous query failover > > > > > > > > > > > > > >> > https://issues.apache.org/jira/browse/IGNITE-426 > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 8. Significant transactional cache performance > > > > > > optimizations > > > > > > > > - I > > > > > > > > > > > will > > > > > > > > > > > > > >> merge > > > > > > > > > > > > > >> these changes from > 'ignite-1.4-slow-server-debug' > > > > today > > > > > or > > > > > > > > > > tomorrow. > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes. > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> 10. I would also like to include distributed > > > > Semaphore. > > > > > > > > > Vladislav, > > > > > > > > > > > any > > > > > > > > > > > > > >> chance you can finish with it this week? > > > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE- > > > > > > > > > > > > > >> < > https://issues.apache.org/jira/browse/IGNITE-426 > > > >638 > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> Thanks to everyone involved! Guys, esp. > assignees > > of > > > > > > > mentioned > > > > > > > > > > > issues, > > > > > > > > > > > > > >> please respond to this email and let us know > when > > > can > > > > we > > > > > > > > expect > > > > > > > > > > your > > > > > > > > > > > > > >> changes being merged to master and release > branch? > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> Can someone create ignite-1.5 release branch? > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> --Yakov > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >
