From dev-return-48846-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Dec 24 07:28:43 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 C13A818065E for ; Tue, 24 Dec 2019 08:28:42 +0100 (CET) Received: (qmail 89951 invoked by uid 500); 24 Dec 2019 07:28:41 -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 89939 invoked by uid 99); 24 Dec 2019 07:28:41 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Dec 2019 07:28:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id CB0481A346B for ; Tue, 24 Dec 2019 07:28:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-ec2-va.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 2qfpLQhHA5v7 for ; Tue, 24 Dec 2019 07:28:39 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.217.52; helo=mail-vs1-f52.google.com; envelope-from=ilya.kasnacheev@gmail.com; receiver= Received: from mail-vs1-f52.google.com (mail-vs1-f52.google.com [209.85.217.52]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 1408FBC53C for ; Tue, 24 Dec 2019 07:28:39 +0000 (UTC) Received: by mail-vs1-f52.google.com with SMTP id b4so11622795vsa.12 for ; Mon, 23 Dec 2019 23:28:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=KiEynExm4dIS6ZLHN/WiYkY3gHp+NXJYI9AQPQwY4dc=; b=OmZ3yPYM/OqllZehDlEeOEZeLKS88lsDpLx0RCYCEu/W+iegdKImMSRtsVIajXxI+N HBWx3sV7fD/0XAWKB0Hexp8vC4nbnS8Ekb+OCXYEZzzbGQOHU/1PWpdDF2kIcbTdyhCS hhKkzcCZBwHmdmHJW0O+hme2Se3h9/W/4B7v9YYdLpmMwvABkoVsp/yArZehTSjnBCDg lTl99X2JhHqdBXfpynxnb/eTPwdfPA/RT+rjZeAk9dY+xc2CovFL8JmMzgtA4BsgDUlM 5wIv2r9yONzTSX7HBa6SjWyXx4OCiRWMR+nE+tAX53wM0cOVNfqDp64El0SYOzJX7ILp u/Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=KiEynExm4dIS6ZLHN/WiYkY3gHp+NXJYI9AQPQwY4dc=; b=HOrdf5MeIHvmQFFLiQ4mNb4vuJymYeBGPNggHMLI6LlY/J7ua0pS5jMdxGa2OUa8vs v/32trZfyQY8wcpmSr7+mWNLA4BspEBIzLZ2xGpSZqX+0Csda3xlQKWhBAzShAhv/RDo YAVlqJLbkeHkouHRQp8QZG9U2oYF2mRVAgwX8aYSCMbu7Vm1cjoK3f9oUt45b5k1q3ZW Yv9+Pkjt9jhpWJ38c0fFgw+hlvaV1Ub4BEikAFwF0XfgFaHKY8K+pdKynrUW9ZX4dZ96 5pQcMeUDJIYnTwZXQ2oesrwazyMtuOYWaTYdSRSYeJvSiui1sInAkdXDQAJ2lWceu7U7 EhBA== X-Gm-Message-State: APjAAAXeR4nsBLZ35AIINFgjthDwuioaIou3OQhvAPs+VH9d+J3skSpd kL6aWc8LkRGfFy61SebMqMVHKVWHVKZ52BlzlCuBZlHq X-Google-Smtp-Source: APXvYqwANWmcQM+Zl/9UXI/WsiOfkDoXnnxtev8rYmGbPUI6CLywaSPTtvLVZQW17Ov/Uw+K3KaWHeqX8KIz9atJdU4= X-Received: by 2002:a67:6a43:: with SMTP id f64mr12674741vsc.195.1577172518200; Mon, 23 Dec 2019 23:28:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ilya Kasnacheev Date: Tue, 24 Dec 2019 10:28:26 +0300 Message-ID: Subject: Re: Let's remove ignite-schedule module and IgniteScheduler interface To: dev Content-Type: multipart/alternative; boundary="000000000000b269ac059a6e1758" --000000000000b269ac059a6e1758 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello! I did not find the exact information but I can confirm that ignite-schedule 1.0.0 may see some downloads, but that's all. Since 1.0.0 we don't publish this artifact so its usage also remains a mystery. Regards, --=20 Ilya Kasnacheev =D0=BF=D0=BD, 23 =D0=B4=D0=B5=D0=BA. 2019 =D0=B3. =D0=B2 22:37, Denis Magda= : > https://repository.apache.org > > At least Ignite PMC has access to data. > > - > Denis > > > On Mon, Dec 23, 2019 at 11:35 AM Ilya Kasnacheev < > ilya.kasnacheev@gmail.com> > wrote: > > > Hello! > > > > Can you guide me where these downloads are from? We don't seem to publi= sh > > ignite-schedule to Maven Central since early 1.x. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > =D1=81=D0=B1, 21 =D0=B4=D0=B5=D0=BA. 2019 =D0=B3. =D0=B2 03:20, Denis M= agda : > > > > > Ilya, good points, then support the idea of the API removal in 3.0. > > > > > > Ivan, downloaded the screenshot to Google Drive: > > > > > > > > > https://drive.google.com/file/d/1N21N7yqCbeZtCNs1sHvJLiJfHF_Hp0wd/view?us= p=3Dsharing > > > > > > > > > - > > > Denis > > > > > > > > > On Fri, Dec 20, 2019 at 7:09 AM Ilya Kasnacheev < > > ilya.kasnacheev@gmail.com > > > > > > > wrote: > > > > > > > Hello! > > > > > > > > This module has two obvious downsides: > > > > > > > > - It's LGPL. > > > > - It can only schedule locally. > > > > > > > > We could fix 1) by using other implementation, but given 2) this no > > > longer > > > > sounds feasible. If someone wants to use local scheduler, why not > just > > > use > > > > it directly? > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > > > > > > > > =D0=BF=D1=82, 20 =D0=B4=D0=B5=D0=BA. 2019 =D0=B3. =D0=B2 10:26, Iva= n Pavlukhin : > > > > > > > > > Denis, > > > > > > > > > > > The API is definitely used with even higher demand for the last > > > months > > > > > (overall the demand is comparable to Ignite Kafka and ML). See > > > > attachment. > > > > > I do not see the attachement. Where can I find it? > > > > > > > > > > =D1=87=D1=82, 19 =D0=B4=D0=B5=D0=BA. 2019 =D0=B3. =D0=B2 20:01, D= enis Magda : > > > > > > > > > > > > The API is definitely used with even higher demand for the last > > > months > > > > > (overall the demand is comparable to Ignite Kafka and ML). See > > > > attachment. > > > > > > > > > > > > If the module has some problems let's discuss them separately a= nd > > see > > > > > how to approach first. Do we have a list of the issues tracked > > > anywhere? > > > > > > > > > > > > > > > > > > - > > > > > > Denis > > > > > > > > > > > > > > > > > > On Thu, Dec 19, 2019 at 8:52 AM Valentin Kulichenko < > > > > > valentin.kulichenko@gmail.com> wrote: > > > > > >> > > > > > >> Ivan, > > > > > >> > > > > > >> IGFS and Hadoop Accelerator had inherent architectural flaws - > the > > > > vast > > > > > >> majority of users who tried to use these features failed to > > achieve > > > > > >> expected results. And yes, at the same time the interest was > very > > > > high, > > > > > so > > > > > >> we really needed to take action :) > > > > > >> > > > > > >> Scheduler module, on the other hand, works as expected and mig= ht > > be > > > > > used by > > > > > >> someone. There is no need to hurry. > > > > > >> > > > > > >> It probably makes sense to deprecate the functionality in 2.8 = so > > > that > > > > > users > > > > > >> are aware of upcoming removal. But the removal itself should > > happen > > > in > > > > > the > > > > > >> major release. > > > > > >> > > > > > >> -Val > > > > > >> > > > > > >> On Thu, Dec 19, 2019 at 12:09 AM Ivan Pavlukhin < > > > vololo100@gmail.com> > > > > > wrote: > > > > > >> > > > > > >> > Guys, > > > > > >> > > > > > > >> > Why some of us are so critical regarding the subject? If I > > recall > > > > > >> > correctly we decided to drop IGFS and Hadoop support before > 2.8 > > > > > >> > without much debate. And it was a feature users were > interested > > > in. > > > > I > > > > > >> > never saw an interest to IgniteSchedule. My statistics is > based > > on > > > > our > > > > > >> > User mailing list. > > > > > >> > > > > > > >> > =D1=87=D1=82, 19 =D0=B4=D0=B5=D0=BA. 2019 =D0=B3. =D0=B2 11:= 00, Alexey Kuznetsov < > > > > akuznetsov@apache.org > > > > > >: > > > > > >> > > > > > > > >> > > I will vote "+1" for 3.0 > > > > > >> > > > > > > > >> > > On Thu, Dec 19, 2019 at 10:57 AM Anton Vinogradov < > > > av@apache.org> > > > > > wrote: > > > > > >> > > > > > > > >> > > > My Vote was for 3.0 > > > > > >> > > > > > > > > >> > > > On Thu, Dec 19, 2019 at 10:44 AM Valentin Kulichenko < > > > > > >> > > > valentin.kulichenko@gmail.com> wrote: > > > > > >> > > > > > > > > >> > > > > Is this suggested for 3.0 or 2.8? > > > > > >> > > > > > > > > > >> > > > > I tend to agree with Alexey - API compatibility should > be > > > > > preserved > > > > > >> > > > within > > > > > >> > > > > a major version. I would oppose doing such a change in > > 2.x. > > > > > >> > > > > > > > > > >> > > > > If this is planned for 3.0, then it's a definite +1 fr= om > > me. > > > > > >> > > > > > > > > > >> > > > > -Val > > > > > >> > > > > > > > > > >> > > > > On Wed, Dec 18, 2019 at 11:34 PM Alexey Kuznetsov < > > > > > >> > akuznetsov@apache.org > > > > > >> > > > > > > > > > >> > > > > wrote: > > > > > >> > > > > > > > > > >> > > > > > Hi! > > > > > >> > > > > > > > > > > >> > > > > > What if some users already using this module? > > > > > >> > > > > > What they should do? Rewrite code? > > > > > >> > > > > > I do not think it is a good idea. > > > > > >> > > > > > > > > > > >> > > > > > My "-1" here. > > > > > >> > > > > > > > > > > >> > > > > > On Thu, Dec 19, 2019 at 8:53 AM Anton Vinogradov < > > > > > av@apache.org> > > > > > >> > > > wrote: > > > > > >> > > > > > > > > > > >> > > > > > > ignite-schedule does not look to be properly locat= ed > > or > > > > > useful. > > > > > >> > > > > > > My +1 here. > > > > > >> > > > > > > > > > > > >> > > > > > > On Thu, Dec 19, 2019 at 8:35 AM Ivan Pavlukhin < > > > > > >> > vololo100@gmail.com> > > > > > >> > > > > > > wrote: > > > > > >> > > > > > > > > > > > >> > > > > > > > Ilya, > > > > > >> > > > > > > > > > > > > >> > > > > > > > I think it is a good initiative! Do we really ne= ed > > to > > > > keep > > > > > >> > > > > > > > run/callLocall methods at all? > > > > > >> > > > > > > > > > > > > >> > > > > > > > =D1=81=D1=80, 18 =D0=B4=D0=B5=D0=BA. 2019 =D0=B3= . =D0=B2 17:59, Ilya Kasnacheev < > > > > > ilyak@apache.org > > > > > >> > >: > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > Hello! > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > Since 2.8 is branched, I want to initiate the > > > > discussion > > > > > >> > about > > > > > >> > > > > > removal > > > > > >> > > > > > > of > > > > > >> > > > > > > > > ignite-schedule module. > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > My plan as follows: > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > Remove ignite-schedule module entirely. > > > > > >> > > > > > > > > Move runLocal and callLocal methods from > > > > > IgniteScheduler to > > > > > >> > > > > > > > IgniteCompute. > > > > > >> > > > > > > > > Delete IgniteScheduler interface with its > > remaining > > > > > >> > > > scheduleLocal() > > > > > >> > > > > > > > methods. > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > Rationale: Ignite is not a tool for local > > > scheduling, > > > > > >> > > > > IgniteScheduler > > > > > >> > > > > > > > does > > > > > >> > > > > > > > > not provide any means of remote scheduling, an= d > I > > > > don't > > > > > think > > > > > >> > > > > anybody > > > > > >> > > > > > > is > > > > > >> > > > > > > > > using that (especially since ignite-schedule i= s > > > > > unpublished > > > > > >> > LGPL > > > > > >> > > > > > > module). > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > I would like to hear opinions as well as > positive > > > and > > > > > >> > negative > > > > > >> > > > > votes > > > > > >> > > > > > > > > towards this. If I won't see any activity, I > will > > go > > > > > forward > > > > > >> > with > > > > > >> > > > > > JIRA > > > > > >> > > > > > > > > issue. > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > Previous discussion: > > > > > >> > > > > > https://issues.apache.org/jira/browse/IGNITE-5565 > > > > > >> > > > > > > > > We tried to move it to Quartz but it changed > > > semantics > > > > > in > > > > > >> > some > > > > > >> > > > > ways. > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > Regards, > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > -- > > > > > >> > > > > > > > Best regards, > > > > > >> > > > > > > > Ivan Pavlukhin > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > > >> > > > > > -- > > > > > >> > > > > > Alexey Kuznetsov > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > > >> > > -- > > > > > >> > > Alexey Kuznetsov > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > -- > > > > > >> > Best regards, > > > > > >> > Ivan Pavlukhin > > > > > >> > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best regards, > > > > > Ivan Pavlukhin > > > > > > > > > > > > > > > --000000000000b269ac059a6e1758--