From dev-return-46720-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Jul 22 19:50:57 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id A8EA918064F for ; Mon, 22 Jul 2019 21:50:56 +0200 (CEST) Received: (qmail 58099 invoked by uid 500); 22 Jul 2019 19:50:55 -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 58088 invoked by uid 99); 22 Jul 2019 19:50:55 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jul 2019 19:50:55 +0000 Received: from mail-io1-f53.google.com (mail-io1-f53.google.com [209.85.166.53]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 8028F829F for ; Mon, 22 Jul 2019 19:50:55 +0000 (UTC) Received: by mail-io1-f53.google.com with SMTP id s7so76561468iob.11 for ; Mon, 22 Jul 2019 12:50:55 -0700 (PDT) X-Gm-Message-State: APjAAAVWTyiMh3rab91YKFdjM+7Bo4EhHOGDp8ec0H0g2KBtVLxzV2/Y 8kDHJLJfi3quDF09QDotOcqgY9M+I6yK9Y8+S0wBcg== X-Google-Smtp-Source: APXvYqzdVcDg8ZFcvlCMsfrvquacGI38ANSZWXB7R6LFsz/RWR0RzDiFKkBghOtt1TVHLbOgazEkGJrAdTlb62t3vuw= X-Received: by 2002:a5d:8e08:: with SMTP id e8mr70627417iod.139.1563825054993; Mon, 22 Jul 2019 12:50:54 -0700 (PDT) MIME-Version: 1.0 References: <4fd5beacff05fdd88aaceb74a6115b186eb0f92f.camel@nobitlost.com> In-Reply-To: From: Denis Magda Date: Mon, 22 Jul 2019 12:51:13 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSSION] Ignite 3.0 and to be removed list To: dev Content-Type: multipart/alternative; boundary="000000000000e4ea65058e4a64a8" --000000000000e4ea65058e4a64a8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Igniters, I did the first run through the wishlist and selected integrations and APIs for discontinuation. My suggestion would be to use IEP-36 (Modularization) page for the final list that we'll send to the user list for feedback: - Integrations for discontinuation: https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularizat= ion#IEP-36:Modularization-IntegrationsforDiscontinuation - APIs for removal: https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularizat= ion#IEP-36:Modularization-APIsforRemoval Please check those lists and let us know if you have any arguments against discontinuation/removal of X. Also, if you believe that something listed in the wishlist should be added to the EIP then let's discuss that. Personally, I see the whishlist as a page with ideas while the IEP a final plan for action. - Denis On Mon, Jul 22, 2019 at 12:05 AM Vyacheslav Daradur wrote: > I think all agreed items should be marked @Deprecated in the code > base, so we will be able to remove them transparently for the > end-users. > > On Mon, Jul 22, 2019 at 9:32 AM =D0=9F=D0=B0=D0=B2=D0=BB=D1=83=D1=85=D0= =B8=D0=BD =D0=98=D0=B2=D0=B0=D0=BD wrote: > > > > Alex, > > > > I already added a couple of items to wishlist [1]. > > > > Yes, I agree that the process should be iterative. But I am confused > > on what stage we are in a current interation? I suppose that Denis is > > going to present a list of removal candidates which we as developers > > agreed on. And should not we have that list already available > > somewhere as a document? Now I see an infromation scattered in this > > thread and the wishlist [1]. And it is not easy to me to realize where > > we are now. > > > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wish= list > > > > =D1=87=D1=82, 18 =D0=B8=D1=8E=D0=BB. 2019 =D0=B3. =D0=B2 18:14, Alexey = Goncharuk < > alexey.goncharuk@gmail.com>: > > > > > > Ivan, > > > > > > The list is not final, we can still discuss and add more points to be > > > cleaned in 3.0. The more clear and understandable the API will be, th= e > > > better. This thread was intended to draft the removal scope for 3.0 > and to > > > understand which portions will be definitely removed. > > > > > > > > > =D1=81=D1=80, 17 =D0=B8=D1=8E=D0=BB. 2019 =D0=B3. =D0=B2 15:26, =D0= =9F=D0=B0=D0=B2=D0=BB=D1=83=D1=85=D0=B8=D0=BD =D0=98=D0=B2=D0=B0=D0=BD : > > > > > > > Also, I did not quite get the point about JSR107 (JCache). From tim= e > > > > to time I see on user-list threads where Ignite is used along with > > > > Spring annotation-based cache integration. I suppose it requires > > > > JCache interfaces. What is crucially wrong with supporting it? > > > > > > > > =D1=81=D1=80, 17 =D0=B8=D1=8E=D0=BB. 2019 =D0=B3. =D0=B2 15:19, =D0= =9F=D0=B0=D0=B2=D0=BB=D1=83=D1=85=D0=B8=D0=BD =D0=98=D0=B2=D0=B0=D0=BD : > > > > > > > > > > Folks, > > > > > > > > > > Sorry if I am repeating something. I checked a page [1] and have > not > > > > > found several items. > > > > > 1. I thought that there was an agreement of dropping OLD service > grid, > > > > > was not it? > > > > > 2. Also IndexingSpi seems to me as a candidate for removal. > > > > > > > > > > Should I add those items to the page? Or is there another page > > > > > containing items to be removed that we agreed on? > > > > > > > > > > [1] > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wish= list > > > > > > > > > > =D1=81=D1=80, 17 =D0=B8=D1=8E=D0=BB. 2019 =D0=B3. =D0=B2 02:00, D= enis Magda : > > > > > > > > > > > > Alex, Igniters, sorry for a delay. Got swamped with other dutie= s. > > > > > > > > > > > > Does it wait till the next week? I'll make sure to dedicate som= e > time > > > > for > > > > > > that. Or if we'd like to run faster then I'll appreciate if > someone > > > > else > > > > > > steps in and prepares a list this week. I'll help to review and > > > > solidify it. > > > > > > > > > > > > - > > > > > > Denis > > > > > > > > > > > > > > > > > > On Tue, Jul 16, 2019 at 7:58 AM Alexey Goncharuk < > > > > alexey.goncharuk@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Denis, > > > > > > > > > > > > > > Are we ready to present the list to the user list? > > > > > > > > > > > > > > =D0=B2=D1=82, 2 =D0=B8=D1=8E=D0=BB. 2019 =D0=B3. =D0=B2 00:27= , Denis Magda : > > > > > > > > > > > > > > > I wouldn't kick off dozens of voting discussions. Instead, > the > > > > content on > > > > > > > > the wiki page needs to be cleaned and rearranged. This will > make > > > > the > > > > > > > > content readable and comprehensible. I can do that. > > > > > > > > > > > > > > > > Next, let's ask the user community for an opinion. After > reviewing > > > > and > > > > > > > > incorporating the latter we can do one more dev list > discussion > > > > with the > > > > > > > > last call for opinions. Next, will be the voting time. If > there is > > > > a > > > > > > > > feature someone from the dev list is against of removing, > then we > > > > can > > > > > > > start > > > > > > > > a separate vote for it later. But let's get into those case= s > first. > > > > > > > > > > > > > > > > - > > > > > > > > Denis > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 1, 2019 at 1:47 AM Dmitriy Pavlov < > dpavlov@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > > > I propose each removal should have separated formal vote > thread > > > > with > > > > > > > > > consensus approval (since it is code modification). > > > > > > > > > > > > > > > > > > This means a single binding objection with justification > is a > > > > blocker > > > > > > > for > > > > > > > > > removal. > > > > > > > > > > > > > > > > > > We need separation to let community members pick up an > > > > interesting > > > > > > > topic > > > > > > > > > from email subject. Not all members reading carefully eac= h > post > > > > in > > > > > > > > > mile-long threads. > > > > > > > > > > > > > > > > > > =D0=BF=D0=BD, 1 =D0=B8=D1=8E=D0=BB. 2019 =D0=B3. =D0=B2 1= 1:17, Anton Vinogradov < > av@apache.org>: > > > > > > > > > > > > > > > > > > > +1 to email survey with following types of votes > > > > > > > > > > - silence (agree with all proposed removals) > > > > > > > > > > - we have to keep XXX because ... > > > > > > > > > > > > > > > > > > > > As a result, will gain lists > > > > > > > > > > "to be removed" - no one objected > > > > > > > > > > "can be removed" - single objection > > > > > > > > > > "should be kept" - multi objections > > > > > > > > > > > > > > > > > > > > Denis or Dmitry Pavlov, could you please lead this > thread? > > > > > > > > > > > > > > > > > > > > On Sat, Jun 29, 2019 at 12:27 AM Denis Magda < > > > > dmagda@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Alex, > > > > > > > > > > > > > > > > > > > > > > I would do an email survey to hear an opinion of why > someone > > > > > > > > believes a > > > > > > > > > > > feature A has to stay. It makes sense to ask about th= e > APIs > > > > to be > > > > > > > > > removed > > > > > > > > > > > as well as integrations to go out of community suppor= t > [1] > > > > in the > > > > > > > > same > > > > > > > > > > > thread. > > > > > > > > > > > > > > > > > > > > > > Has everyone expressed an opinion? If yes, I can go > ahead and > > > > > > > format > > > > > > > > > the > > > > > > > > > > > wishlist page and make it structured for the user > thread. > > > > > > > > > > > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Modularizati= on-td42486.html > > > > > > > > > > > - > > > > > > > > > > > Denis > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jun 28, 2019 at 8:54 AM Alexey Goncharuk < > > > > > > > > > > > alexey.goncharuk@gmail.com> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Anton, good point. > > > > > > > > > > > > > > > > > > > > > > > > Do you have any idea how we can keep track of the > voting? > > > > Should > > > > > > > we > > > > > > > > > > > launch > > > > > > > > > > > > a google survey or survey monkey? Voting by email? > > > > > > > > > > > > > > > > > > > > > > > > =D0=BF=D1=82, 28 =D0=B8=D1=8E=D0=BD. 2019 =D0=B3. = =D0=B2 11:24, Anton Vinogradov < > > > > av@apache.org>: > > > > > > > > > > > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > > > > > > > > > > > Thank's for keeping an eye on page updates. > > > > > > > > > > > > > Near Caches is not a bad feature, but it should b= e > used > > > > with > > > > > > > > > caution. > > > > > > > > > > > > > At least we have to explain how it works on > readme.io, > > > > why and > > > > > > > > > when > > > > > > > > > > it > > > > > > > > > > > > > should be used because usage can drop the > performance > > > > instead > > > > > > > of > > > > > > > > > > > > increasing > > > > > > > > > > > > > it. > > > > > > > > > > > > > > > > > > > > > > > > > > Anyway, I added near caches because I never heard > > > > someone used > > > > > > > > them > > > > > > > > > > > > > meaningfully, not like a silver bullet. > > > > > > > > > > > > > So, that's just a proposal :) > > > > > > > > > > > > > > > > > > > > > > > > > > Also, I'd like to propose to have some voting > about full > > > > list > > > > > > > > later > > > > > > > > > > to > > > > > > > > > > > > gain > > > > > > > > > > > > > "must be removed", "can be removed" and "should b= e > kept" > > > > lists. > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jun 27, 2019 at 1:03 PM Alexey Goncharuk = < > > > > > > > > > > > > > alexey.goncharuk@gmail.com> > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Anton, > > > > > > > > > > > > > > > > > > > > > > > > > > > > I would like to pull-up the discussion regardin= g > the > > > > near > > > > > > > > caches > > > > > > > > > - > > > > > > > > > > I > > > > > > > > > > > > > cannot > > > > > > > > > > > > > > agree this is a feature that needs to be > removed. Near > > > > caches > > > > > > > > > > provide > > > > > > > > > > > > > > significant read performance improvements and, > to the > > > > best of > > > > > > > > my > > > > > > > > > > > > > knowledge, > > > > > > > > > > > > > > are used in several cases in production. Can yo= u > > > > elaborate on > > > > > > > > the > > > > > > > > > > > > > > shortcomings you faced? Maybe we can improve bo= th > > > > internal > > > > > > > code > > > > > > > > > and > > > > > > > > > > > > user > > > > > > > > > > > > > > experience? > > > > > > > > > > > > > > > > > > > > > > > > > > > > =D0=BF=D1=82, 21 =D0=B8=D1=8E=D0=BD. 2019 =D0= =B3. =D0=B2 10:42, Dmitry Melnichuk < > > > > > > > > > > > > > > dmitry.melnichuk@nobitlost.com>: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dmitry, > > > > > > > > > > > > > > > As a Python thin client developer, I think th= at > > > > separate > > > > > > > > > > repository > > > > > > > > > > > > is > > > > > > > > > > > > > > > a truly great idea! > > > > > > > > > > > > > > > On Tue, 2019-06-18 at 21:29 +0300, Dmitriy > Pavlov > > > > wrote: > > > > > > > > > > > > > > > > - Move to separate repositories: thin > clients (at > > > > least > > > > > > > > > > non-Java > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ones) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best regards, > > > > > Ivan Pavlukhin > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > > > -- > Best Regards, Vyacheslav D. > --000000000000e4ea65058e4a64a8--