From dev-return-47823-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Oct 3 20:07:05 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 1FEEA18065B for ; Thu, 3 Oct 2019 22:07:05 +0200 (CEST) Received: (qmail 10952 invoked by uid 500); 3 Oct 2019 20:07:04 -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 10785 invoked by uid 99); 3 Oct 2019 20:07:03 -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; Thu, 03 Oct 2019 20:07:03 +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 41181C1E80 for ; Thu, 3 Oct 2019 20:07:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.799 X-Spam-Level: ** X-Spam-Status: No, score=2.799 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, FREEMAIL_REPLY=1, HTML_MESSAGE=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: spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id f47_qfz_cKN3 for ; Thu, 3 Oct 2019 20:07:01 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.208.43; helo=mail-ed1-f43.google.com; envelope-from=ilya.kasnacheev@gmail.com; receiver= Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com [209.85.208.43]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id A11DFBC5CE for ; Thu, 3 Oct 2019 19:41:14 +0000 (UTC) Received: by mail-ed1-f43.google.com with SMTP id l21so3703819edr.5 for ; Thu, 03 Oct 2019 12:41:14 -0700 (PDT) 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=YwuSro1ylzr0Cmw6mwjjk9GX+QoCqvkKQC4if9gk6bU=; b=C+plApLzx+Tk3iP9aAsTd4yBlmOIFC/IHOdVDUMjFx16PB9fZu/sS4HQjTNHgpG5VT vz527tOZB0oeJdXq+h2lRiHhSFLmXKCifc4ORK0YDI5p+l8kGzdt6DTjvR5ppCV8SHB0 I48fbv0fLHxAUUlu4MDOsZb/8Lzkq5rnrc2Y9Dgsrqp02uzetl16cm5H+mq2EJ/SGC/r B8A4YEZZYw/RdSvOwj3nTvFg0dIGSGYS5Fdqv3dwL8elzfgjhefTCeVNw+lJS3UVyF+7 yXmTzoIQpnnE/Hx4ilQv37QnEn7sa+KRz2hVL5dhlwiCtVoYkLFs+P7mqJw49PLtMbT6 C6Zg== 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=YwuSro1ylzr0Cmw6mwjjk9GX+QoCqvkKQC4if9gk6bU=; b=a8eXmZFmLtVFBFrjlJqRORxJz0H/AfVpJsWDSW1ZNXZ1rgTF9D7RdxEIOVk/MAlX1r 7naGOuopKdb+771ZG7OeHWaMQqNH3WjLm412xmUCB4uon9dAwtFy9AxHqku5oFaCxUt/ GUIvrQU30OqcrMRuf+Pv5+Z+vPpMNy0osEmfSrHsV/0IN95SRLsHXSt5KyOCT5aIVTTC DIOFH0UOcPp3KSr/2f8DW+HZ/kD9DyPEzjiejidIe0/Tzxw48se4t+6jK89kf/f8jUn1 jAabrlW+lDkj7hyxw21lqE/M20ch0iKK/B2Q2i6gwuPmV7hLBQeEyurvrCLxBvr7vlbF ig2w== X-Gm-Message-State: APjAAAW62Mu5hrPjkouLiKdc1Jx5jDtxWTTPdWEjX+elCORGyLGgo8EE tRlLtbePMxDa3O77A0gFhoAT7JJvdgToW3eXeVo6Bg== X-Google-Smtp-Source: APXvYqxZlyQJAMhJ9F58bygzOketBoKpE6pCkDWpeqypsjAe1FaDXG5cMx/ggf76qGgWNjX9Qh+5s8IGT8NrCZv9DA8= X-Received: by 2002:a50:9e08:: with SMTP id z8mr11557232ede.305.1570131667797; Thu, 03 Oct 2019 12:41:07 -0700 (PDT) MIME-Version: 1.0 References: <8657281565622613@sas2-ce04c18c415c.qloud-c.yandex.net> <1566890216.224076930@f387.i.mail.ru> <071e5ffa0a127353e38c4cb1b479f8f706d3f7df.camel@gmail.com> In-Reply-To: From: Ilya Kasnacheev Date: Thu, 3 Oct 2019 22:40:55 +0300 Message-ID: Subject: Re: Replacing default work dir from tmp to current dir To: dev Content-Type: multipart/alternative; boundary="0000000000004f4c2a059406c431" --0000000000004f4c2a059406c431 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello! We can try and fallback to home dir with warning, when file cannot be created in current dir. WDYT? Regards, --=20 Ilya Kasnacheev =D1=87=D1=82, 3 =D0=BE=D0=BA=D1=82. 2019 =D0=B3. =D0=B2 20:05, Pavel Tupits= yn : > > Cannot tell about NuGet. Maven is typically used during development, > usually there is no Maven in production deployments. > NuGet and Maven are very similar. Yes, both of them are build-time tools, > production is unrelated. > For production-ready deployments we can expect users to tweak Ignite to > their needs, set custom storage dirs, adjust heap sizes and so on. > > I'm talking about new users, about "getting started" scenarios - > it is super important to make Ignite easy to get started with, provide > reasonable defaults for all the configuration properties. > > For Ignite.NET, LINQPad is one of those "get started in 2 clicks" > scenarios. And this scenario got broken as explained above. > 2.7.5 and earlier used temp dir, which worked. 2.7.6 fails: "Work directo= ry > does not exist and cannot be created: C:\Program > Files\LINQPad5\ignite\work" > > For Java there is JPad, which will fail in the same way - when you run co= de > from there, `user.dir` points to Program Files. > > I expect that there are more use cases like this, and `user.home` is a > reasonable solution. > > On Thu, Oct 3, 2019 at 5:56 PM Ilya Kasnacheev > wrote: > > > Hello! > > > > I want to point out that I didn't change this location (current dir). I= t > > was already implemented when I raised this issue, the only change I did > was > > to swap current dir/work to current dir/ignite/work to avoid confusion > > whose work dir that is. > > > > I also communicated this to you all in ML when I discovered that curren= t > > dir is used. > > > > I think that current dir is actually *well defined* when starting a > > project. A project is expected to be started from the same dir, and all > > "Run..." dialogs usually allow specifying that one. > > > > For embedded scenarios, you definitely not want work dir from two > different > > Ignite-using tools to interfere. For embedded scenarios, you should onl= y > > expect that current dir is writable. > > > > Even after these considerations, it's too late to change that because > > people don't expect this dir to move with every release of Ignite, and = we > > already did it once. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > =D1=87=D1=82, 3 =D0=BE=D0=BA=D1=82. 2019 =D0=B3. =D0=B2 17:34, Alexey G= oncharuk >: > > > > > > > > > > Seems, we should have different defaults and even distributions for > > > > different usage scenarios. > > > > > > > I still do not understand why defaults should be different for embedd= ed > > and > > > "traditional RDBMS-like" installations. Having different defaults wil= l > > > likely confuse users, not make usability easier. Personally, I would > > forbid > > > to start Ignite if IGNITE_HOME is not set, but this suggestion was no= t > > > accepted by the community. > > > > > > As far as I know, both rocksdb and SQLite is local only libraries and > > don't > > > > have any distrubted features. > > > > > > See no difference here. Imagine a user starts only one Ignite node fo= r > > > development or just to play (which, I believe, happes quite a lot) - > same > > > as with local databases. BTW, it is impossible to start SQLite withou= t > > > database path, so a user either provides a full path, or a relative > path > > > from the current directory - which is an explicit action from a user. > > > > > > > > > > I agree with you. > > > > How it happens, that after wide discussion we implemented, reviewed > and > > > > merged wrong defaults? > > > > > > > > As I know, we have explicit release only to change this default. > > > > > > > > This release is broken, isn't it? > > > > > > > I think this is just a miscommunication. Ilya made a fix which was > > exactly > > > what he meant it to be. As for the release - it may have worse > usability, > > > but not more 'broken' as the previous one with the temp directory. At > > least > > > the data will not be physically removed after the machine restart. > > > > > > --0000000000004f4c2a059406c431--