From dev-return-23406-apmail-ignite-dev-archive=ignite.apache.org@ignite.apache.org Tue Jul 4 10:20:31 2017 Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED31D1A2BA for ; Tue, 4 Jul 2017 10:20:30 +0000 (UTC) Received: (qmail 91156 invoked by uid 500); 4 Jul 2017 10:20:30 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 91106 invoked by uid 500); 4 Jul 2017 10:20:30 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 91094 invoked by uid 99); 4 Jul 2017 10:20:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Jul 2017 10:20:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id F0F4BC08B5 for ; Tue, 4 Jul 2017 10:20:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.792 X-Spam-Level: *** X-Spam-Status: No, score=3.792 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 7KvG6U6yRVaP for ; Tue, 4 Jul 2017 10:20:24 +0000 (UTC) Received: from mail-ua0-f180.google.com (mail-ua0-f180.google.com [209.85.217.180]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 6EA745FB40 for ; Tue, 4 Jul 2017 10:20:23 +0000 (UTC) Received: by mail-ua0-f180.google.com with SMTP id z22so124094470uah.1 for ; Tue, 04 Jul 2017 03:20:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=vUrvnjn9w+OBjWRyWq8cMNig0ST60WaHtcSpsl1OGYk=; b=zVr9ea8G+M6sa76fvSwve70yC8hIYuctE1PKQatjS1MAFXo1aQsgb1TVyZSKrVF5jh 0dkxOj1WTnw3IDW1rdcZAmpPJ3KdxBjxc2gHBkrMtMYPLBaHnXHx5735L3W3HuH6U5QS fzNBl7AWDRSpYn06kLQPHjtbpHwgyZMKUulkyryR3oNStlH4obBFvfxDRjFc+ZoMxShR eHmEh0HBZCTkhVuZQOZVfWsVekqgRTAw5WmZ7sx5jH4m9TleR6/F4Ag7L8wxz1eS+aBQ Pl701Z89JI3cTf/BLhSy9GGD+51wKMK/3W7ncKsVZf/qB2CfPr0/sE8xBWMfBSwXwI+L sw8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=vUrvnjn9w+OBjWRyWq8cMNig0ST60WaHtcSpsl1OGYk=; b=lu0Pp/6jJ9dXw0Sz2nIHdTv/rpQsmR5Ksq78nvh/Yk+AvjSfDHGAmIGAwjMgAlhi3S fG+3qwBuLMbchbeG5YaZOf3jI9lVz1wS0FVmkv+afTUEAcePnd8N9QH2Nwn1QWyyyE4b oEZR34mkkzQo1kr4lc71kf6EHSATOUm1HzZwaW+ikhAURgXwZVNFQP8SQwqu56q17tbE 7iA5jyKOUtEPwUNkeXndWMwGctdAn8nz1r4Od+YBj8ql7WVByGBNA2LssaCI4q4jOREq IdET1lPBjxaGC7HVsUgeiAYhMRIfVR2emkOCKIPtJQwKLvzxAsATV9kxPu5fS+236Q63 Fqmg== X-Gm-Message-State: AKS2vOzGri4s5tHTUsFPAxrXxp8H5VEZxui7ktcG4ysldbw7AHfiHfPS FXWMgRgDmdusQTS6t/13q2e+XxBCVA9z X-Received: by 10.176.78.168 with SMTP id l40mr24929961uah.79.1499163622093; Tue, 04 Jul 2017 03:20:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.24.159 with HTTP; Tue, 4 Jul 2017 03:20:21 -0700 (PDT) In-Reply-To: References: <3C1354F7-D394-4B60-936B-0E69DDD22C9F@apache.org> <05f0fb8d-9a7c-8bf1-f868-223b4fc1d525@gridgain.com> <40558953-5F08-4C82-BF03-F0F416C1BE71@apache.org> From: Vladimir Ozerov Date: Tue, 4 Jul 2017 13:20:21 +0300 Message-ID: Subject: Re: Apache Ignite 2.1 scope To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="f403043ed63827ce9205537b3bd6" --f403043ed63827ce9205537b3bd6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Igniters, Persistent store has been merged to master branch! "master-bak" branch was created to keep the state before merge for safety. As release date for 2.1 is mid July, I created "ignite-2.1" branch where we will stabilize the release as usual. Please push features and fixes planned for 2.1 release to this branch. The rest commits should go to master. Vladimir. On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov wrote: > Hi Denis, > > Awesome news! I'll take care of necessary release procedures if nobody > minds. > > Vladimir. > > On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda wrote: > >> Igniters, >> >> It=E2=80=99s time to refresh this abandoned thread and finally rollout o= ut all >> the changes appeared in 2.1. >> >> In addition, recently donated Persistent Store got the green light [1] t= o >> become a part of the master branch (no one asked for extra time to dive >> into its details) and, personally, it=E2=80=99s absolutely fine to make = it >> available in the nearest release. >> >> My proposal is to do the release by mid of July (closer to July 15th). I= s >> there anyone who is ready to take over as a release manager creating the >> page like this [2] and handling all release related activities? >> >> >> [1] http://apache-ignite-developers.2346864.n4.nabble.com/ >> Ignite-Persistent-Store-Ready-for-merge-td19160.html >> [2] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0 >> >> =E2=80=94 >> Denis >> >> > On Jun 1, 2017, at 9:24 AM, Alexander Paschenko < >> alexander.a.paschenko@gmail.com> wrote: >> > >> > IGNITE-5327 Create predefined cache templates for CREATE TABLE command >> > - minor comments left, ETA is Friday. >> > >> > IGNITE-5380 Validate cache QueryEntities in discovery thread - in >> > progress, the meat of code is written, but need to add lots of tests. >> > ETA is Friday. >> > >> > IGNITE-5188 Support AFFINITY KEY keyword for CREATE TABLE command - in >> > progress, made few first small steps, ETA is Friday. >> > >> > Rest is closed/patch available, ignite-4994 has been moved to 2.2. >> > >> > - Alex >> > >> > 2017-06-01 19:03 GMT+03:00 Sergey Chugunov = : >> >> 1. IGNITE-5386 Inactive mode must be forced on starting up grid wit= h >> >> persistence is enabled >> >> It is important improvement to fix critical bug IGNITE-5363. >> >> Working on it, ETA - tomorrow. >> >> 2. IGNITE-5375 New PersistentStoreMetrics, MemoryMetrics interface >> >> improvements >> >> A lot of discussions were on this topic, ticket created only today >> and >> >> requires several days to implement. >> >> >> >> >> >> >> >> On Thu, Jun 1, 2017 at 6:56 PM, Taras Ledkov >> wrote: >> >> >> >>> Folks, >> >>> >> >>> IGNITE-4922 JDBC Driver: renew thin client based solution: >> >>> >> >>> On 2.1 the functionality of the new thin client JDBC driver will be >> >>> between deprecated Ignite thin JDBC and Ignite JDBCv2. >> >>> 1. The most functions of SQL query (include DML) are implemented and >> ready >> >>> for review; >> >>> 2. The most functions of JDBC metadata are implemented and ready for >> >>> review; >> >>> 3. Transactions, batching, streaming, blobs, scrollable / writable >> cursors >> >>> will not be supported in 2.1. >> >>> >> >>> >> >>> >> >>> On 01.06.2017 18:43, Vladimir Ozerov wrote: >> >>> >> >>>> Folks, >> >>>> >> >>>> We are almost reached proposed feature-complete date (June 2), Coul= d >> you >> >>>> please share current status of your major features? >> >>>> >> >>>> On Tue, May 16, 2017 at 3:51 AM, Dmitriy Setrakyan < >> dsetrakyan@apache.org >> >>>>> >> >>>> wrote: >> >>>> >> >>>> Looks a little tight. Let's hope we can make it. >> >>>>> >> >>>>> On Mon, May 15, 2017 at 1:29 PM, Denis Magda >> wrote: >> >>>>> >> >>>>> Well, let me propose the following milestones for 2.1 release then= . >> >>>>>> >> >>>>>> Code freeze: June 2nd. >> >>>>>> Final QA and benchmarking: June 5 - June 8 >> >>>>>> Voting: ~ June 9 >> >>>>>> Release: ~ June 13 >> >>>>>> >> >>>>>> Also I heard H2 has to be released once again to support Ignite= =E2=80=99s >> CREATE >> >>>>>> table command. Think that we should talk to H2 folks to make it >> happen >> >>>>>> in >> >>>>>> June 22nd - June 2nd time frame. >> >>>>>> >> >>>>>> =E2=80=94 >> >>>>>> Denis >> >>>>>> >> >>>>>> On May 11, 2017, at 2:26 AM, Pavel Tupitsyn >> >>>>>>> >> >>>>>> wrote: >> >>>>>> >> >>>>>>> As for .NET, I would propose to concentrate on peer deployment >> >>>>>>> >> >>>>>> (IGNITE-2492) >> >>>>>> >> >>>>>>> and related stuff, like IGNITE-1894 .NET: Delegate support in th= e >> API >> >>>>>>> >> >>>>>> via >> >>>>> >> >>>>>> extension methods. >> >>>>>>> >> >>>>>>> SQL Dependency does not look important to me, we can reschedule >> it for >> >>>>>>> later versions. >> >>>>>>> >> >>>>>>> On Thu, May 11, 2017 at 12:01 PM, Dmitriy Setrakyan < >> >>>>>>> >> >>>>>> dsetrakyan@apache.org> >> >>>>>> >> >>>>>>> wrote: >> >>>>>>> >> >>>>>>> Vyacheslav, I think it is worth the research, but you should >> always >> >>>>>>>> >> >>>>>>> keep >> >>>>> >> >>>>>> data querying and indexing in mind. For example, I don't see how >> >>>>>>>> >> >>>>>>> by-page >> >>>>> >> >>>>>> compression will solve it. >> >>>>>>>> >> >>>>>>>> On Thu, May 11, 2017 at 1:52 AM, Vyacheslav Daradur < >> >>>>>>>> >> >>>>>>> daradurvs@gmail.com> >> >>>>>> >> >>>>>>> wrote: >> >>>>>>>> >> >>>>>>>> Dmitriy, >> >>>>>>>>> >> >>>>>>>>> I'm researching a best way for this future. >> >>>>>>>>> >> >>>>>>>>> At the moment I found only one way (querying and indexing >> >>>>>>>>> >> >>>>>>>> compatible), >> >>>>> >> >>>>>> this >> >>>>>>>> >> >>>>>>>>> is per-objects-field compression. >> >>>>>>>>> >> >>>>>>>>> But there is a good proffit only for long strings or fields wi= th >> >>>>>>>>> >> >>>>>>>> large >> >>>>> >> >>>>>> objects. >> >>>>>>>>> >> >>>>>>>>> Maybe it makes sense just to introduce compression for string >> fileds. >> >>>>>>>>> >> >>>>>>>>> I'm researching the new page-memory architecture as applied to >> >>>>>>>>> >> >>>>>>>> by-page >> >>>>> >> >>>>>> compression. >> >>>>>>>>> >> >>>>>>>>> 2017-05-11 11:30 GMT+03:00 Dmitriy Setrakyan < >> dsetrakyan@apache.org >> >>>>>>>>> >> >>>>>>>> : >> >>>>>> >> >>>>>>> On Thu, May 11, 2017 at 12:44 AM, Vyacheslav Daradur < >> >>>>>>>>>> >> >>>>>>>>> daradurvs@gmail.com> >> >>>>>>>>> >> >>>>>>>>>> wrote: >> >>>>>>>>>> >> >>>>>>>>>> Denis, >> >>>>>>>>>>> >> >>>>>>>>>>> The described roadmap looks great! >> >>>>>>>>>>> >> >>>>>>>>>>> Additional, I vote for introducing an ability (OOTB) to stor= e >> >>>>>>>>>>> >> >>>>>>>>>> objects >> >>>>> >> >>>>>> in >> >>>>>>>>> >> >>>>>>>>>> a >> >>>>>>>>>> >> >>>>>>>>>>> cache in a compressed form. >> >>>>>>>>>>> This will allow to store more data at the cost of incriasing >> of CPU >> >>>>>>>>>>> utilization. >> >>>>>>>>>>> >> >>>>>>>>>>> One of the problems with compression is indexing and >> querying. How >> >>>>>>>>>> >> >>>>>>>>> do >> >>>>> >> >>>>>> we >> >>>>>>>> >> >>>>>>>>> index the data if it is compressed? >> >>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>>> 2017-05-11 4:23 GMT+03:00 Denis Magda : >> >>>>>>>>>>> >> >>>>>>>>>>> Igniters, >> >>>>>>>>>>>> >> >>>>>>>>>>>> Let me start a discussion around the scope for 2.1 release. >> >>>>>>>>>>>> >> >>>>>>>>>>>> In my vision the main direction of our ongoing efforts >> should be >> >>>>>>>>>>>> implementing in life a use case of Ignite as a transactiona= l >> >>>>>>>>>>>> >> >>>>>>>>>>> distributed >> >>>>>>>>>> >> >>>>>>>>>>> SQL database and HTAP platform. The current use cases >> (database >> >>>>>>>>>>>> >> >>>>>>>>>>> cache, >> >>>>>>>>> >> >>>>>>>>>> data >> >>>>>>>>>>> >> >>>>>>>>>>>> grid, micro services platform, etc.) will be supported as >> usual, >> >>>>>>>>>>>> >> >>>>>>>>>>> no >> >>>>> >> >>>>>> changes >> >>>>>>>>>>> >> >>>>>>>>>>>> on that frontier. >> >>>>>>>>>>>> >> >>>>>>>>>>>> Keeping this in mind, the roadmap needs to include essentia= l >> SQL >> >>>>>>>>>>>> >> >>>>>>>>>>> related >> >>>>>>>>>> >> >>>>>>>>>>> features as well as disk based capabilities, MVCC support, >> >>>>>>>>>>>> >> >>>>>>>>>>> advanced >> >>>>> >> >>>>>> DDL >> >>>>>>>>> >> >>>>>>>>>> implementation and so on so forth. This is for Ignite as a SQ= L >> >>>>>>>>>>>> >> >>>>>>>>>>> database. >> >>>>>>>>>> >> >>>>>>>>>>> Next, Machine Learning will be a great addition to Ignite as >> an >> >>>>>>>>>>>> >> >>>>>>>>>>> HTAP >> >>>>>>>> >> >>>>>>>>> platform offering. This is why we should keep investing our ti= me >> >>>>>>>>>>>> >> >>>>>>>>>>> and >> >>>>>>>> >> >>>>>>>>> resources in that recently released component. >> >>>>>>>>>>>> >> >>>>>>>>>>>> Having this said, I see the scope for 2.1 release this way: >> >>>>>>>>>>>> >> >>>>>>>>>>>> 1. Distributed Persistent Store - if the donation is >> accepted by >> >>>>>>>>>>>> >> >>>>>>>>>>> ASF. >> >>>>>>>> >> >>>>>>>>> The >> >>>>>>>>>> >> >>>>>>>>>>> decision is to be done in separate discussion. W/o the store >> >>>>>>>>>>>> Ignite can only be used as In-Memory SQL database. >> >>>>>>>>>>>> >> >>>>>>>>>>>> 2. SQL Grid: >> >>>>>>>>>>>> - CREATE & DROP table commands: >> https://issues.apache.org/ >> >>>>>>>>>>>> jira/browse/IGNITE-4651 >> >>>>>>>>>>>> - Renewed JDBC driver: https://issues.apache.org/ >> >>>>>>>>>>>> jira/browse/IGNITE-4922 >> >>>>>>>>>>>> - Collocation based routing of SQL queries: >> >>>>>>>>>>>> >> >>>>>>>>>>> https://issues.apache.org/ >> >>>>>>>>>>> >> >>>>>>>>>>>> jira/browse/IGNITE-4510, >> >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-4509 >> >>>>>>>>>>>> - >> >>>>>>>>>>>> >> >>>>>>>>>>>> 3. .NET: >> >>>>>>>>>>>> - Peer-class loading: https://issues.apache.org/ >> >>>>>>>>>>>> jira/browse/IGNITE-2492 >> >>>>>>>>>>>> - SQLDependency: https://issues.apache.org/ >> >>>>>>>>>>>> >> >>>>>>>>>>> jira/browse/IGNITE-2657 >> >>>>>>>>> >> >>>>>>>>>> 4. C++: >> >>>>>>>>>>>> - Compute Grid: https://issues.apache.org/ >> >>>>>>>>>>>> >> >>>>>>>>>>> jira/browse/IGNITE-3574 >> >>>>>>>>> >> >>>>>>>>>> 5. ML Grid: >> >>>>>>>>>>>> - Linear regression algorithms: >> https://issues.apache.org/ >> >>>>>>>>>>>> jira/browse/IGNITE-5012 >> >>>>>>>>>>>> - K-means clustering: https://issues.apache.org/ >> >>>>>>>>>>>> jira/browse/IGNITE-5113 >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> Please join the thread and share your thoughts, ideas and >> >>>>>>>>>>>> >> >>>>>>>>>>> concerns. >> >>>>> >> >>>>>> =E2=80=94 >> >>>>>>>>>>>> Denis >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>>>> -- >> >>>>>>>>>>> Best Regards, Vyacheslav >> >>>>>>>>>>> >> >>>>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> -- >> >>>>>>>>> Best Regards, Vyacheslav >> >>>>>>>>> >> >>>>>>>>> >> >>>>>> >> >>> -- >> >>> Taras Ledkov >> >>> Mail-To: tledkov@gridgain.com >> >>> >> >>> >> >> > --f403043ed63827ce9205537b3bd6--