Re: Update and actualize table list of maintainers

[Denis Magda]

Maxim,

I do support this idea. Let me ping my GridGain colleagues. Please, ping
the Sberbank guys.

Saikat, Roman, others, please update the page as well.

-
Denis


On Wed, Oct 2, 2019 at 4:09 AM Maxim Muzafarov  wrote:

> Igniters,
>
>
> Currently and usual we have some issues [2][3] which is waiting for a
> review and it is not easy from the contributor point of view to find
> the right person who will able to review the PR. Of course, the
> dev-list discussion is the right place to ask about a review, but
> nevertheless...
>
> I think the table list of maintainers [1] needs to be updated since it
> is not actual anymore. Can we update this list together?
>
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> [2] https://issues.apache.org/jira/browse/IGNITE-11008
> [3] https://issues.apache.org/jira/browse/IGNITE-11868
>

Re: Update and actualize table list of maintainers

[Anton Vinogradov]

Folks,
I've cleaned the list because 70% of listed people not maintainers anymore.
Feel free to list yourself.

On Thu, Oct 3, 2019 at 2:42 AM Denis Magda  wrote:

> Maxim,
>
> I do support this idea. Let me ping my GridGain colleagues. Please, ping
> the Sberbank guys.
>
> Saikat, Roman, others, please update the page as well.
>
> -
> Denis
>
>
> On Wed, Oct 2, 2019 at 4:09 AM Maxim Muzafarov  wrote:
>
> > Igniters,
> >
> >
> > Currently and usual we have some issues [2][3] which is waiting for a
> > review and it is not easy from the contributor point of view to find
> > the right person who will able to review the PR. Of course, the
> > dev-list discussion is the right place to ask about a review, but
> > nevertheless...
> >
> > I think the table list of maintainers [1] needs to be updated since it
> > is not actual anymore. Can we update this list together?
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > [2] https://issues.apache.org/jira/browse/IGNITE-11008
> > [3] https://issues.apache.org/jira/browse/IGNITE-11868
> >
>

Update and actualize table list of maintainers

[Maxim Muzafarov]

Igniters,


Currently and usual we have some issues [2][3] which is waiting for a
review and it is not easy from the contributor point of view to find
the right person who will able to review the PR. Of course, the
dev-list discussion is the right place to ask about a review, but
nevertheless...

I think the table list of maintainers [1] needs to be updated since it
is not actual anymore. Can we update this list together?


[1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
[2] https://issues.apache.org/jira/browse/IGNITE-11008
[3] https://issues.apache.org/jira/browse/IGNITE-11868

Re: [DISCUSSION][IEP-35] Replace RunningQueryManager with GridSystemViewManager

[Ivan Pavlukhin]

Hi Nikolay,

Actually I do not fully understand what is SystemView API. I have not
found it in IEP [1] (I searched for words "system" and "view").

RunningQueryManager is a component responsible for tracking running
queries internally. This info is exposed to users as SQL view via
SqlSystemViewRunningQueries. In the same package you can find a plenty
of other SQL views.

[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392

вт, 1 окт. 2019 г. в 06:42, Nikolay Izhikov :
>
> Hello, Igniters.
>
> Since the last release `RunningQueryManager` [1] was added.
> It used to track a running query.
>
> In IEP-35 [2] SystemView API was added.
> SystemView API supposed to be used to track all kinds of internal Ignite 
> objects.
>
> I think this RunningQueryManager should be replaced [3] with the more unified 
> SystemView API.
>
> Any objections?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-10754
> [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392
> [3] https://issues.apache.org/jira/browse/IGNITE-12223
> [4] https://issues.apache.org/jira/browse/IGNITE-12224



-- 
Best regards,
Ivan Pavlukhin

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

[Maxim Muzafarov]

Folks,

Since we are focusing on new SQL engine implementation I'd like to
perform bulk moving of all MVCC related unassigned tickets [1] to the
next release.
Can you confirm?

[1] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Ignite%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20fixVersion%20%3D%202.8%20and%20priority%20in%20(Major)%20and%20summary%20~%20MVCC

On Wed, 2 Oct 2019 at 01:27, Denis Magda  wrote:
>
> Alexey Z.,
>
> Could you please answer some of the questions
>
>
> > - IGNITE-11942 IGFS and Hadoop Accelerator Discontinuation [2].
> > Probably should be moved to the next release due to dependency on
> > Tensorflow. Need to check. (Andrey Gura)
>
>
> Can we decouple Tensorflow from the IGFS?
>
> Mark all the issues related to ML, Spark 2.4, Monitoring major
> > features and track their comletion to be sure on there is no
> > unfinished major changes will be present in 2.8 release.
> > - ML (Alexey Zinoviev)
>
>
> Are there any other ML contributors who will be helping you with this
> release?
>
> -
> Denis
>
>
> On Tue, Oct 1, 2019 at 6:56 AM Maxim Muzafarov  wrote:
>
> > Igniters,
> >
> >
> > Here is the list of activities we've agreed on to prepare the Apache
> > Ignite 2.8 release.
> >
> > 1.
> > Preliminary release dates with the ability to shift them if some of
> > the planned activities will not be finalized. But anyway we should
> > build our engagement based on these dates.
> >
> > Scope Freeze: November 5, 2019
> > Code Freeze: December 2, 2019
> > Voting Date: January 10, 2020
> > Release Date: January 17, 2020
> >
> > 2.
> > Mark all the issues related to ML, Spark 2.4, Monitoring major
> > features and track their comletion to be sure on there is no
> > unfinished major changes will be present in 2.8 release.
> > - ML (Alexey Zinoviev)
> > - Spark [1] [4] (Alexey Zinoviev)
> > - Monitoring (Nikolay Izhikov)
> >
> > 3.
> > Review and mark all the partially completed major issues currently
> > present in the master branch.
> > - major IEPs e.g. IEP-18, non-blocking PME (Maxim Muzafarov)
> > - review major commits in the master branch (Maxim Muzafarov)
> >
> > 4.
> > Review blocker issues currently pinned to 2.8 release.
> > - IGNITE-11942 IGFS and Hadoop Accelerator Discontinuation [2].
> > Probably should be moved to the next release due to dependency on
> > Tensorflow. Need to check. (Andrey Gura)
> > - IGNITE-9489 CorruptedTreeException on index create [3]. Check all
> > the issues releated to this. Some of them already fixed by GridGain.
> > Need to check. (Andrey Gura)
> > - IGNITE-12181 Rebalance hangs on BLT change. The cause has been
> > found. Will be fixed. (Maxim Muzafarov)
> > - Need to check all the other blocker issues (Maxim Muzafarov)
> >
> > 5.
> > QA regression (2.7 -> 2.8). I'll provide additional details when I'll get
> > them.
> > Review and check test-cases, optioannly schedule meeting (Maxim Muzafarov)
> >
> > 6.
> > (optional) Need to create an INFRA ticket to add `Epic` JIRA issue
> > type to the Apache Ignite JIRA. The issue [6] has been created but not
> > sure that I have the right permission to do so.
> >
> > [1]
> > http://apache-ignite-developers.2346864.n4.nabble.com/The-Spark-2-4-support-td43777.html
> > [2] https://issues.apache.org/jira/browse/IGNITE-11942
> > [3] https://issues.apache.org/jira/browse/IGNITE-9489
> > [4] https://issues.apache.org/jira/browse/IGNITE-12054
> > [5] https://issues.apache.org/jira/browse/IGNITE-12181
> > [6] https://issues.apache.org/jira/browse/INFRA-19164
> >
> > On Mon, 30 Sep 2019 at 12:14, Ivan Pavlukhin  wrote:
> > >
> > > Maxim, Folks,
> > >
> > > Could you please share a results of the Slack discussion from Sep 25?
> > >
> > > ср, 25 сент. 2019 г. в 15:50, Dmitriy Pavlov :
> > > >
> > > > Hi Maxim,
> > > >
> > > > Thank you for preparing the release page!
> > > >
> > > > Could you please add Require release notes filter? You can find an
> > example
> > > > in
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> > > >
> > > > Sincerely
> > > > Dmitriy Pavlov
> > > >
> > > > ср, 25 сент. 2019 г. в 11:58, Maxim Muzafarov :
> > > >
> > > > > Igniters,
> > > > >
> > > > >
> > > > > It's true that we are still discussing the release dates. But
> > > > > nevertheless, all the release blockers are important since some of
> > > > > them may require more than one month to be fixed. Let's discuss today
> > > > > how we will handle these issues and track Monitoring and ML major
> > > > > features to get them into the next release.
> > > > >
> > > > > The meeting already scheduled. We will use the ASF Slack on September
> > > > > 25-th, 17-00 (MSK).
> > > > > I've created the channel [2] #ignite-release-2_8 please, join.
> > > > > (Discussion will be on Russin language).
> > > > >
> > > > >
> > > > >
> > > > > Please, also note that I've created the 2.8 release confluence page
> > > > > [1] with additional information. I will review all the issues we have
> > > > > and will move some o

Re: Replacing default work dir from tmp to current dir

[Pavel Tupitsyn]

Igniters,

Looks like we made a mistake while implementing IGNITE-12057:
`user.dir` is NOT user home directory, it is where JVM has been started
from, which is rather arbitrary.
(Among other things this breaks Ignite.NET usage from tools like LINQPad,
because `user.dir` ends up pointing to Program Files, which is not
writable without elevation)

We should use `user.home` system property instead, see
https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html

Thoughts, objections?

On Mon, Sep 2, 2019 at 1:57 PM Ilya Kasnacheev 
wrote:

> Hello again!
>
> Please note that I have updated release notes for IGNITE-12057 as well as
> added them for my ticket. Release Engineers, please make sure you include
> the latest one.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 2 сент. 2019 г. в 13:33, Ilya Kasnacheev :
>
> > Hello!
> >
> > I have pushed an amended fix to both master and ignite-2.7.6.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пт, 30 авг. 2019 г. в 21:48, Denis Magda :
> >
> >> Ilya,
> >>
> >> I forgot to push "Send for review" button. You can see my minor comment
> >> now.
> >>
> >> -
> >> Denis
> >>
> >>
> >> On Fri, Aug 30, 2019 at 5:47 AM Ilya Kasnacheev <
> >> ilya.kasnach...@gmail.com>
> >> wrote:
> >>
> >> > Hello!
> >> >
> >> > Waiting for a minor comment from Denis, as soon as I see/fix it I'm
> >> going
> >> > to commit.
> >> >
> >> > Regards,
> >> > Ilya.
> >> > --
> >> > Ilya Kasnacheev
> >> >
> >> >
> >> > пт, 30 авг. 2019 г. в 11:30, Alexey Goncharuk <
> >> alexey.goncha...@gmail.com
> >> > >:
> >> >
> >> > > Hello Ilya,
> >> > >
> >> > > Just curious, when are you planning to commit your changes to the
> >> 2.7.6
> >> > > branch?
> >> > >
> >> > > ср, 28 авг. 2019 г. в 04:57, Denis Magda :
> >> > >
> >> > > > Ok, seems like we came to a consensus. Let’s ensure that the path
> >> for
> >> > our
> >> > > > work dir is user.dir/ignite/work and restart the vote.
> >> > > >
> >> > > > Denis
> >> > > >
> >> > > > On Tuesday, August 27, 2019, Ilya Kasnacheev <
> >> > ilya.kasnach...@gmail.com>
> >> > > > wrote:
> >> > > >
> >> > > > > Hello!
> >> > > > >
> >> > > > > I have took the liberty to implement the change to existing code
> >> base
> >> > > to
> >> > > > > remove concern about work/ directory:
> >> > > > >
> >> > > > > https://github.com/apache/ignite/pull/6816/files
> >> > > > >
> >> > > > > Some advocacy for this patch:
> >> > > > > - Minimal change.
> >> > > > > - Storing in user.dir/ignite/work (current directory, e.g.
> project
> >> > > root)
> >> > > > > which is consistent with behavior of unzipped binary release.
> >> > > > > - We can re-use user.dir/ignite for other uses in the future,
> >> such as
> >> > > > > storing logs there.
> >> > > > >
> >> > > > > I have to admit that my previous reaction to the change was too
> >> > strong.
> >> > > > It
> >> > > > > turned out the default was user.dir/work (project root) and not
> >> > > > > user.home/work (home dir with imminent Work collision).
> >> > > > > Nevertheless, I think that after this change it would be good
> >> enough
> >> > to
> >> > > > > last for a few years.
> >> > > > >
> >> > > > > What do you think?
> >> > > > >
> >> > > > > Regards,
> >> > > > > --
> >> > > > > Ilya Kasnacheev
> >> > > > >
> >> > > > >
> >> > > > > вт, 27 авг. 2019 г. в 18:28, Alexey Goncharuk <
> >> > > > alexey.goncha...@gmail.com
> >> > > > > >:
> >> > > > >
> >> > > > > > In the current state of the project, we cannot directly
> compare
> >> > > Ignite
> >> > > > > > setup process to the one of postgresql or another database. In
> >> many
> >> > > > > Ignite
> >> > > > > > examples, an embedded node (even with persistence) is started
> >> and
> >> > it
> >> > > is
> >> > > > > > supposed to run without any additional FS rights grants or
> init
> >> > > steps.
> >> > > > > This
> >> > > > > > may be changed in 3.0, but not in a maintenance release. If we
> >> are
> >> > to
> >> > > > > > change the directory to /var/lib, I would rather fail Ignite
> >> node
> >> > > start
> >> > > > > > asking a user to explicitly provide work directory path. Let
> >> alone
> >> > > > > /var/lib
> >> > > > > > is not portable and I would not add an OS-switch to the code
> >> for no
> >> > > > > reason.
> >> > > > > >
> >> > > > > > I vote for storing the work in ~/ignite/work - agree with Ilya
> >> that
> >> > > > > writing
> >> > > > > > large amounts of data in a hidden folder is a bad idea.
> >> > > > > >
> >> > > > > > вт, 27 авг. 2019 г. в 15:17, Dmitriy Pavlov <
> dpav...@apache.org
> >> >:
> >> > > > > >
> >> > > > > > > Hi Igniters,
> >> > > > > > >
> >> > > > > > > I agree that user home maybe not the best place from Linux
> >> > > > perspective
> >> > > > > > and
> >> > > > > > > philosophy, but  "user.home"/ignite/work  is more or less
> >> > portable.
> >> > > > > > >
> >> > > > > > > For the Linux environment, we can add a suggestion about
> >> where to
> >> > > > place
> >> > > > > > > persisted data. For very first 

Re: Replacing default work dir from tmp to current dir

[Ilya Kasnacheev]

Hello!

I think this is a sensible default and it was certainly not chosen by
mistake. It was intentional expectation that your project is started from
project root and data is located under it.

If this breaks .Net, I am deeply sorry.
However, I think we should change .net to provide non-default workdir
location when none is specified.

Can you please clarify scenarios that are broken now?

Regards,

ср, 2 окт. 2019 г., 20:28 Pavel Tupitsyn :

> Igniters,
>
> Looks like we made a mistake while implementing IGNITE-12057:
> `user.dir` is NOT user home directory, it is where JVM has been started
> from, which is rather arbitrary.
> (Among other things this breaks Ignite.NET usage from tools like LINQPad,
> because `user.dir` ends up pointing to Program Files, which is not
> writable without elevation)
>
> We should use `user.home` system property instead, see
> https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html
>
> Thoughts, objections?
>
> On Mon, Sep 2, 2019 at 1:57 PM Ilya Kasnacheev 
> wrote:
>
> > Hello again!
> >
> > Please note that I have updated release notes for IGNITE-12057 as well as
> > added them for my ticket. Release Engineers, please make sure you include
> > the latest one.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 2 сент. 2019 г. в 13:33, Ilya Kasnacheev  >:
> >
> > > Hello!
> > >
> > > I have pushed an amended fix to both master and ignite-2.7.6.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > пт, 30 авг. 2019 г. в 21:48, Denis Magda :
> > >
> > >> Ilya,
> > >>
> > >> I forgot to push "Send for review" button. You can see my minor
> comment
> > >> now.
> > >>
> > >> -
> > >> Denis
> > >>
> > >>
> > >> On Fri, Aug 30, 2019 at 5:47 AM Ilya Kasnacheev <
> > >> ilya.kasnach...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hello!
> > >> >
> > >> > Waiting for a minor comment from Denis, as soon as I see/fix it I'm
> > >> going
> > >> > to commit.
> > >> >
> > >> > Regards,
> > >> > Ilya.
> > >> > --
> > >> > Ilya Kasnacheev
> > >> >
> > >> >
> > >> > пт, 30 авг. 2019 г. в 11:30, Alexey Goncharuk <
> > >> alexey.goncha...@gmail.com
> > >> > >:
> > >> >
> > >> > > Hello Ilya,
> > >> > >
> > >> > > Just curious, when are you planning to commit your changes to the
> > >> 2.7.6
> > >> > > branch?
> > >> > >
> > >> > > ср, 28 авг. 2019 г. в 04:57, Denis Magda :
> > >> > >
> > >> > > > Ok, seems like we came to a consensus. Let’s ensure that the
> path
> > >> for
> > >> > our
> > >> > > > work dir is user.dir/ignite/work and restart the vote.
> > >> > > >
> > >> > > > Denis
> > >> > > >
> > >> > > > On Tuesday, August 27, 2019, Ilya Kasnacheev <
> > >> > ilya.kasnach...@gmail.com>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Hello!
> > >> > > > >
> > >> > > > > I have took the liberty to implement the change to existing
> code
> > >> base
> > >> > > to
> > >> > > > > remove concern about work/ directory:
> > >> > > > >
> > >> > > > > https://github.com/apache/ignite/pull/6816/files
> > >> > > > >
> > >> > > > > Some advocacy for this patch:
> > >> > > > > - Minimal change.
> > >> > > > > - Storing in user.dir/ignite/work (current directory, e.g.
> > project
> > >> > > root)
> > >> > > > > which is consistent with behavior of unzipped binary release.
> > >> > > > > - We can re-use user.dir/ignite for other uses in the future,
> > >> such as
> > >> > > > > storing logs there.
> > >> > > > >
> > >> > > > > I have to admit that my previous reaction to the change was
> too
> > >> > strong.
> > >> > > > It
> > >> > > > > turned out the default was user.dir/work (project root) and
> not
> > >> > > > > user.home/work (home dir with imminent Work collision).
> > >> > > > > Nevertheless, I think that after this change it would be good
> > >> enough
> > >> > to
> > >> > > > > last for a few years.
> > >> > > > >
> > >> > > > > What do you think?
> > >> > > > >
> > >> > > > > Regards,
> > >> > > > > --
> > >> > > > > Ilya Kasnacheev
> > >> > > > >
> > >> > > > >
> > >> > > > > вт, 27 авг. 2019 г. в 18:28, Alexey Goncharuk <
> > >> > > > alexey.goncha...@gmail.com
> > >> > > > > >:
> > >> > > > >
> > >> > > > > > In the current state of the project, we cannot directly
> > compare
> > >> > > Ignite
> > >> > > > > > setup process to the one of postgresql or another database.
> In
> > >> many
> > >> > > > > Ignite
> > >> > > > > > examples, an embedded node (even with persistence) is
> started
> > >> and
> > >> > it
> > >> > > is
> > >> > > > > > supposed to run without any additional FS rights grants or
> > init
> > >> > > steps.
> > >> > > > > This
> > >> > > > > > may be changed in 3.0, but not in a maintenance release. If
> we
> > >> are
> > >> > to
> > >> > > > > > change the directory to /var/lib, I would rather fail Ignite
> > >> node
> > >> > > start
> > >> > > > > > asking a user to explicitly provide work directory path. Let
> > >> alone
> > >> > > > > /var/lib
> > >> > > > > > is not portable and I would not add an OS-switch to the code
> > >> 

Re: Replacing default work dir from tmp to current dir

[Pavel Tupitsyn]

Everyone above agreed to `~/ignite/work`, then somehow we jumped to
`user.dir/ignite/work`.
To me `user.dir` looked like synonym for ~, but turns out this is not true.
I think others may be confused in the same way.

Denis Magda, Alexey Goncharuk, and others - please confirm that you
understand that `user.dir` means current directory, not user home directory.

In my opinion, this is very broken. Current work dir can be literally
anything, e.g.:
`cd / && ~/my-ignite-app/run.sh` will cause an attempt to create ignite dir
in system root, and so on.



On Wed, Oct 2, 2019 at 9:46 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> I think this is a sensible default and it was certainly not chosen by
> mistake. It was intentional expectation that your project is started from
> project root and data is located under it.
>
> If this breaks .Net, I am deeply sorry.
> However, I think we should change .net to provide non-default workdir
> location when none is specified.
>
> Can you please clarify scenarios that are broken now?
>
> Regards,
>
> ср, 2 окт. 2019 г., 20:28 Pavel Tupitsyn :
>
> > Igniters,
> >
> > Looks like we made a mistake while implementing IGNITE-12057:
> > `user.dir` is NOT user home directory, it is where JVM has been started
> > from, which is rather arbitrary.
> > (Among other things this breaks Ignite.NET usage from tools like LINQPad,
> > because `user.dir` ends up pointing to Program Files, which is not
> > writable without elevation)
> >
> > We should use `user.home` system property instead, see
> >
> https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html
> >
> > Thoughts, objections?
> >
> > On Mon, Sep 2, 2019 at 1:57 PM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com>
> > wrote:
> >
> > > Hello again!
> > >
> > > Please note that I have updated release notes for IGNITE-12057 as well
> as
> > > added them for my ticket. Release Engineers, please make sure you
> include
> > > the latest one.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > пн, 2 сент. 2019 г. в 13:33, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> > >:
> > >
> > > > Hello!
> > > >
> > > > I have pushed an amended fix to both master and ignite-2.7.6.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > пт, 30 авг. 2019 г. в 21:48, Denis Magda :
> > > >
> > > >> Ilya,
> > > >>
> > > >> I forgot to push "Send for review" button. You can see my minor
> > comment
> > > >> now.
> > > >>
> > > >> -
> > > >> Denis
> > > >>
> > > >>
> > > >> On Fri, Aug 30, 2019 at 5:47 AM Ilya Kasnacheev <
> > > >> ilya.kasnach...@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > Hello!
> > > >> >
> > > >> > Waiting for a minor comment from Denis, as soon as I see/fix it
> I'm
> > > >> going
> > > >> > to commit.
> > > >> >
> > > >> > Regards,
> > > >> > Ilya.
> > > >> > --
> > > >> > Ilya Kasnacheev
> > > >> >
> > > >> >
> > > >> > пт, 30 авг. 2019 г. в 11:30, Alexey Goncharuk <
> > > >> alexey.goncha...@gmail.com
> > > >> > >:
> > > >> >
> > > >> > > Hello Ilya,
> > > >> > >
> > > >> > > Just curious, when are you planning to commit your changes to
> the
> > > >> 2.7.6
> > > >> > > branch?
> > > >> > >
> > > >> > > ср, 28 авг. 2019 г. в 04:57, Denis Magda :
> > > >> > >
> > > >> > > > Ok, seems like we came to a consensus. Let’s ensure that the
> > path
> > > >> for
> > > >> > our
> > > >> > > > work dir is user.dir/ignite/work and restart the vote.
> > > >> > > >
> > > >> > > > Denis
> > > >> > > >
> > > >> > > > On Tuesday, August 27, 2019, Ilya Kasnacheev <
> > > >> > ilya.kasnach...@gmail.com>
> > > >> > > > wrote:
> > > >> > > >
> > > >> > > > > Hello!
> > > >> > > > >
> > > >> > > > > I have took the liberty to implement the change to existing
> > code
> > > >> base
> > > >> > > to
> > > >> > > > > remove concern about work/ directory:
> > > >> > > > >
> > > >> > > > > https://github.com/apache/ignite/pull/6816/files
> > > >> > > > >
> > > >> > > > > Some advocacy for this patch:
> > > >> > > > > - Minimal change.
> > > >> > > > > - Storing in user.dir/ignite/work (current directory, e.g.
> > > project
> > > >> > > root)
> > > >> > > > > which is consistent with behavior of unzipped binary
> release.
> > > >> > > > > - We can re-use user.dir/ignite for other uses in the
> future,
> > > >> such as
> > > >> > > > > storing logs there.
> > > >> > > > >
> > > >> > > > > I have to admit that my previous reaction to the change was
> > too
> > > >> > strong.
> > > >> > > > It
> > > >> > > > > turned out the default was user.dir/work (project root) and
> > not
> > > >> > > > > user.home/work (home dir with imminent Work collision).
> > > >> > > > > Nevertheless, I think that after this change it would be
> good
> > > >> enough
> > > >> > to
> > > >> > > > > last for a few years.
> > > >> > > > >
> > > >> > > > > What do you think?
> > > >> > > > >
> > > >> > > > > Regards,
> > > >> > > > > --
> > > >> > > > > Ilya Kasnacheev
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > вт, 27 авг. 201

Re: Ignite community is building Calcite-based prototype

[Julian Hyde]

Denis,

I’ve been a follower and admirer of Ignite for several years, so I am delighted 
that you are considering Calcite.

Ask questions on the dev list, log JIRA cases if you find them, and we’ll do 
our best to help.

I’d like to bring to your attention RelBuilder. Some people want to go from SQL 
text to executable plan, but others want to drop in at the relational algebra 
level, and RelBuilder is a convenient interface for the latter.

(The other) Julian


> On Oct 1, 2019, at 3:43 PM, Denis Magda  wrote:
> 
> Hi Julian,
> 
> Nice to e-meet you and thanks for being ready to help! Hopefully, the
> Ignite community will be able to contribute valuable changes back to
> Calcite as part of this activity - "pay good for good" :)
> 
> You are right that distributed computing, massive-parallel processing, and
> calculations/querying at scale is what Ignite is targeted for. However,
> while Drill is designed for analytics and IoTDB is for time-series, Ignite
> is primarily used for OLTP with an increasing number of real-time analytics
> use cases (no adhoc).
> 
> Let's stay in touch!
> 
> -
> Denis
> 
> 
> On Tue, Oct 1, 2019 at 6:42 AM Julian Feinauer 
> wrote:
> 
>> Hi Igor,
>> 
>> I agree that it should be rather similar to what Drill did as distributed
>> computing also is a big concern for Ignite, I guess, right?
>> 
>> Julian
>> 
>> Am 01.10.19, 15:06 schrieb "Seliverstov Igor" :
>> 
>>Guys,
>> 
>>The better link:
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine
>> <
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-37:+New+query+execution+engine
>>> 
>> 
>>Almost everything you may see by the link is the same as Drill guys
>> already did, the difference is in details but the idea is the same.
>> 
>>Of course we’ll face many issues while development and I'll appreciate
>> if some of you assist us.
>> 
>>Regards,
>>Igor
>> 
>>> 1 окт. 2019 г., в 12:32, Julian Feinauer <
>> j.feina...@pragmaticminds.de> написал(а):
>>> 
>>> Hi Denis,
>>> 
>>> Nice to hear from you and the ignite team... that sounds like an
>> excellent idea. I liked the idea of Ignite since I heard about it (I think
>> when it became TLP back then). So I would be happy to help you if you have
>> specific questions... I‘m currently working on a related topic, namely
>> integrate calcite as SQL Layer into Apache IoTDB .
>>> 
>>> Best
>>> Julian
>>> 
>>> Holen Sie sich Outlook für iOS
>>> 
>>> Von: Denis Magda 
>>> Gesendet: Tuesday, October 1, 2019 2:37:20 AM
>>> An: d...@calcite.apache.org ; dev <
>> dev@ignite.apache.org>
>>> Betreff: Ignite community is building Calcite-based prototype
>>> 
>>> Hey ASF-mates,
>>> 
>>> Just wanted to send a note for Ignite dev community who has started
>>> prototyping
>>> <
>> http://apache-ignite-developers.2346864.n4.nabble.com/New-SQL-execution-engine-td43724.html
>>> 
>>> with a new Ignite SQL engine and Calcite was selected as the most
>> favorable
>>> option.
>>> 
>>> We will truly appreciate if you help us with questions that might
>> hit your
>>> dev list. Ignite folks have already studied Calcite well enough and
>> carried
>>> on with the integration, but there might be tricky parts that would
>> require
>>> your expertise.
>>> 
>>> Btw, if anybody is interested in Ignite (memory-centric database and
>>> compute platform) or would like to learn more details about the
>> prototype
>>> or join its development, please check these links or send us a note:
>>> 
>>>  - https://ignite.apache.org
>>>  -
>>> 
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-33%3A+New+SQL+executor+engine+infrastructure
>>> 
>>> 
>>> -
>>> Denis,
>>> Ignite PMC Chair
>> 
>> 
>> 
>> 

Re: Ignite community is building Calcite-based prototype

[Denis Magda]

Julian,

Thanks a lot for the references and guidance! I do believe that from now on
our community guys will become frequent visitors of yours ;)

-
Denis


On Wed, Oct 2, 2019 at 12:40 PM Julian Hyde  wrote:

> Denis,
>
> I’ve been a follower and admirer of Ignite for several years, so I am
> delighted that you are considering Calcite.
>
> Ask questions on the dev list, log JIRA cases if you find them, and we’ll
> do our best to help.
>
> I’d like to bring to your attention RelBuilder. Some people want to go
> from SQL text to executable plan, but others want to drop in at the
> relational algebra level, and RelBuilder is a convenient interface for the
> latter.
>
> (The other) Julian
>
>
> > On Oct 1, 2019, at 3:43 PM, Denis Magda  wrote:
> >
> > Hi Julian,
> >
> > Nice to e-meet you and thanks for being ready to help! Hopefully, the
> > Ignite community will be able to contribute valuable changes back to
> > Calcite as part of this activity - "pay good for good" :)
> >
> > You are right that distributed computing, massive-parallel processing,
> and
> > calculations/querying at scale is what Ignite is targeted for. However,
> > while Drill is designed for analytics and IoTDB is for time-series,
> Ignite
> > is primarily used for OLTP with an increasing number of real-time
> analytics
> > use cases (no adhoc).
> >
> > Let's stay in touch!
> >
> > -
> > Denis
> >
> >
> > On Tue, Oct 1, 2019 at 6:42 AM Julian Feinauer <
> j.feina...@pragmaticminds.de>
> > wrote:
> >
> >> Hi Igor,
> >>
> >> I agree that it should be rather similar to what Drill did as
> distributed
> >> computing also is a big concern for Ignite, I guess, right?
> >>
> >> Julian
> >>
> >> Am 01.10.19, 15:06 schrieb "Seliverstov Igor" :
> >>
> >>Guys,
> >>
> >>The better link:
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine
> >> <
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-37:+New+query+execution+engine
> >>>
> >>
> >>Almost everything you may see by the link is the same as Drill guys
> >> already did, the difference is in details but the idea is the same.
> >>
> >>Of course we’ll face many issues while development and I'll
> appreciate
> >> if some of you assist us.
> >>
> >>Regards,
> >>Igor
> >>
> >>> 1 окт. 2019 г., в 12:32, Julian Feinauer <
> >> j.feina...@pragmaticminds.de> написал(а):
> >>>
> >>> Hi Denis,
> >>>
> >>> Nice to hear from you and the ignite team... that sounds like an
> >> excellent idea. I liked the idea of Ignite since I heard about it (I
> think
> >> when it became TLP back then). So I would be happy to help you if you
> have
> >> specific questions... I‘m currently working on a related topic, namely
> >> integrate calcite as SQL Layer into Apache IoTDB .
> >>>
> >>> Best
> >>> Julian
> >>>
> >>> Holen Sie sich Outlook für iOS
> >>> 
> >>> Von: Denis Magda 
> >>> Gesendet: Tuesday, October 1, 2019 2:37:20 AM
> >>> An: d...@calcite.apache.org ; dev <
> >> dev@ignite.apache.org>
> >>> Betreff: Ignite community is building Calcite-based prototype
> >>>
> >>> Hey ASF-mates,
> >>>
> >>> Just wanted to send a note for Ignite dev community who has started
> >>> prototyping
> >>> <
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/New-SQL-execution-engine-td43724.html
> >>>
> >>> with a new Ignite SQL engine and Calcite was selected as the most
> >> favorable
> >>> option.
> >>>
> >>> We will truly appreciate if you help us with questions that might
> >> hit your
> >>> dev list. Ignite folks have already studied Calcite well enough and
> >> carried
> >>> on with the integration, but there might be tricky parts that would
> >> require
> >>> your expertise.
> >>>
> >>> Btw, if anybody is interested in Ignite (memory-centric database and
> >>> compute platform) or would like to learn more details about the
> >> prototype
> >>> or join its development, please check these links or send us a note:
> >>>
> >>>  - https://ignite.apache.org
> >>>  -
> >>>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-33%3A+New+SQL+executor+engine+infrastructure
> >>>
> >>>
> >>> -
> >>> Denis,
> >>> Ignite PMC Chair
> >>
> >>
> >>
> >>
>
>

Re: Replacing default work dir from tmp to current dir

[Denis Magda]

I was always expecting this to be a user *home* directory that can be
resolved in any operating system and will work for any language supported
by Ignite. So, I'm with Pavel here.

Alex G, what's your thinking? Sounds like we need to change this one more
time.

-
Denis


On Wed, Oct 2, 2019 at 12:17 PM Pavel Tupitsyn  wrote:

> Everyone above agreed to `~/ignite/work`, then somehow we jumped to
> `user.dir/ignite/work`.
> To me `user.dir` looked like synonym for ~, but turns out this is not true.
> I think others may be confused in the same way.
>
> Denis Magda, Alexey Goncharuk, and others - please confirm that you
> understand that `user.dir` means current directory, not user home
> directory.
>
> In my opinion, this is very broken. Current work dir can be literally
> anything, e.g.:
> `cd / && ~/my-ignite-app/run.sh` will cause an attempt to create ignite dir
> in system root, and so on.
>
>
>
> On Wed, Oct 2, 2019 at 9:46 PM Ilya Kasnacheev 
> wrote:
>
> > Hello!
> >
> > I think this is a sensible default and it was certainly not chosen by
> > mistake. It was intentional expectation that your project is started from
> > project root and data is located under it.
> >
> > If this breaks .Net, I am deeply sorry.
> > However, I think we should change .net to provide non-default workdir
> > location when none is specified.
> >
> > Can you please clarify scenarios that are broken now?
> >
> > Regards,
> >
> > ср, 2 окт. 2019 г., 20:28 Pavel Tupitsyn :
> >
> > > Igniters,
> > >
> > > Looks like we made a mistake while implementing IGNITE-12057:
> > > `user.dir` is NOT user home directory, it is where JVM has been started
> > > from, which is rather arbitrary.
> > > (Among other things this breaks Ignite.NET usage from tools like
> LINQPad,
> > > because `user.dir` ends up pointing to Program Files, which is not
> > > writable without elevation)
> > >
> > > We should use `user.home` system property instead, see
> > >
> >
> https://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html
> > >
> > > Thoughts, objections?
> > >
> > > On Mon, Sep 2, 2019 at 1:57 PM Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com>
> > > wrote:
> > >
> > > > Hello again!
> > > >
> > > > Please note that I have updated release notes for IGNITE-12057 as
> well
> > as
> > > > added them for my ticket. Release Engineers, please make sure you
> > include
> > > > the latest one.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > пн, 2 сент. 2019 г. в 13:33, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com
> > > >:
> > > >
> > > > > Hello!
> > > > >
> > > > > I have pushed an amended fix to both master and ignite-2.7.6.
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > пт, 30 авг. 2019 г. в 21:48, Denis Magda :
> > > > >
> > > > >> Ilya,
> > > > >>
> > > > >> I forgot to push "Send for review" button. You can see my minor
> > > comment
> > > > >> now.
> > > > >>
> > > > >> -
> > > > >> Denis
> > > > >>
> > > > >>
> > > > >> On Fri, Aug 30, 2019 at 5:47 AM Ilya Kasnacheev <
> > > > >> ilya.kasnach...@gmail.com>
> > > > >> wrote:
> > > > >>
> > > > >> > Hello!
> > > > >> >
> > > > >> > Waiting for a minor comment from Denis, as soon as I see/fix it
> > I'm
> > > > >> going
> > > > >> > to commit.
> > > > >> >
> > > > >> > Regards,
> > > > >> > Ilya.
> > > > >> > --
> > > > >> > Ilya Kasnacheev
> > > > >> >
> > > > >> >
> > > > >> > пт, 30 авг. 2019 г. в 11:30, Alexey Goncharuk <
> > > > >> alexey.goncha...@gmail.com
> > > > >> > >:
> > > > >> >
> > > > >> > > Hello Ilya,
> > > > >> > >
> > > > >> > > Just curious, when are you planning to commit your changes to
> > the
> > > > >> 2.7.6
> > > > >> > > branch?
> > > > >> > >
> > > > >> > > ср, 28 авг. 2019 г. в 04:57, Denis Magda :
> > > > >> > >
> > > > >> > > > Ok, seems like we came to a consensus. Let’s ensure that the
> > > path
> > > > >> for
> > > > >> > our
> > > > >> > > > work dir is user.dir/ignite/work and restart the vote.
> > > > >> > > >
> > > > >> > > > Denis
> > > > >> > > >
> > > > >> > > > On Tuesday, August 27, 2019, Ilya Kasnacheev <
> > > > >> > ilya.kasnach...@gmail.com>
> > > > >> > > > wrote:
> > > > >> > > >
> > > > >> > > > > Hello!
> > > > >> > > > >
> > > > >> > > > > I have took the liberty to implement the change to
> existing
> > > code
> > > > >> base
> > > > >> > > to
> > > > >> > > > > remove concern about work/ directory:
> > > > >> > > > >
> > > > >> > > > > https://github.com/apache/ignite/pull/6816/files
> > > > >> > > > >
> > > > >> > > > > Some advocacy for this patch:
> > > > >> > > > > - Minimal change.
> > > > >> > > > > - Storing in user.dir/ignite/work (current directory, e.g.
> > > > project
> > > > >> > > root)
> > > > >> > > > > which is consistent with behavior of unzipped binary
> > release.
> > > > >> > > > > - We can re-use user.dir/ignite for other uses in the
> > future,
> > > > >> such as
> > > > >> > > > > storing logs there.
> > > > >> > > > >
> >

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

[Denis Magda]

Maxim,

This sounds reasonable to me.

-
Denis


On Wed, Oct 2, 2019 at 8:55 AM Maxim Muzafarov  wrote:

> Folks,
>
> Since we are focusing on new SQL engine implementation I'd like to
> perform bulk moving of all MVCC related unassigned tickets [1] to the
> next release.
> Can you confirm?
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Ignite%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20fixVersion%20%3D%202.8%20and%20priority%20in%20(Major)%20and%20summary%20~%20MVCC
>
> On Wed, 2 Oct 2019 at 01:27, Denis Magda  wrote:
> >
> > Alexey Z.,
> >
> > Could you please answer some of the questions
> >
> >
> > > - IGNITE-11942 IGFS and Hadoop Accelerator Discontinuation [2].
> > > Probably should be moved to the next release due to dependency on
> > > Tensorflow. Need to check. (Andrey Gura)
> >
> >
> > Can we decouple Tensorflow from the IGFS?
> >
> > Mark all the issues related to ML, Spark 2.4, Monitoring major
> > > features and track their comletion to be sure on there is no
> > > unfinished major changes will be present in 2.8 release.
> > > - ML (Alexey Zinoviev)
> >
> >
> > Are there any other ML contributors who will be helping you with this
> > release?
> >
> > -
> > Denis
> >
> >
> > On Tue, Oct 1, 2019 at 6:56 AM Maxim Muzafarov 
> wrote:
> >
> > > Igniters,
> > >
> > >
> > > Here is the list of activities we've agreed on to prepare the Apache
> > > Ignite 2.8 release.
> > >
> > > 1.
> > > Preliminary release dates with the ability to shift them if some of
> > > the planned activities will not be finalized. But anyway we should
> > > build our engagement based on these dates.
> > >
> > > Scope Freeze: November 5, 2019
> > > Code Freeze: December 2, 2019
> > > Voting Date: January 10, 2020
> > > Release Date: January 17, 2020
> > >
> > > 2.
> > > Mark all the issues related to ML, Spark 2.4, Monitoring major
> > > features and track their comletion to be sure on there is no
> > > unfinished major changes will be present in 2.8 release.
> > > - ML (Alexey Zinoviev)
> > > - Spark [1] [4] (Alexey Zinoviev)
> > > - Monitoring (Nikolay Izhikov)
> > >
> > > 3.
> > > Review and mark all the partially completed major issues currently
> > > present in the master branch.
> > > - major IEPs e.g. IEP-18, non-blocking PME (Maxim Muzafarov)
> > > - review major commits in the master branch (Maxim Muzafarov)
> > >
> > > 4.
> > > Review blocker issues currently pinned to 2.8 release.
> > > - IGNITE-11942 IGFS and Hadoop Accelerator Discontinuation [2].
> > > Probably should be moved to the next release due to dependency on
> > > Tensorflow. Need to check. (Andrey Gura)
> > > - IGNITE-9489 CorruptedTreeException on index create [3]. Check all
> > > the issues releated to this. Some of them already fixed by GridGain.
> > > Need to check. (Andrey Gura)
> > > - IGNITE-12181 Rebalance hangs on BLT change. The cause has been
> > > found. Will be fixed. (Maxim Muzafarov)
> > > - Need to check all the other blocker issues (Maxim Muzafarov)
> > >
> > > 5.
> > > QA regression (2.7 -> 2.8). I'll provide additional details when I'll
> get
> > > them.
> > > Review and check test-cases, optioannly schedule meeting (Maxim
> Muzafarov)
> > >
> > > 6.
> > > (optional) Need to create an INFRA ticket to add `Epic` JIRA issue
> > > type to the Apache Ignite JIRA. The issue [6] has been created but not
> > > sure that I have the right permission to do so.
> > >
> > > [1]
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/The-Spark-2-4-support-td43777.html
> > > [2] https://issues.apache.org/jira/browse/IGNITE-11942
> > > [3] https://issues.apache.org/jira/browse/IGNITE-9489
> > > [4] https://issues.apache.org/jira/browse/IGNITE-12054
> > > [5] https://issues.apache.org/jira/browse/IGNITE-12181
> > > [6] https://issues.apache.org/jira/browse/INFRA-19164
> > >
> > > On Mon, 30 Sep 2019 at 12:14, Ivan Pavlukhin 
> wrote:
> > > >
> > > > Maxim, Folks,
> > > >
> > > > Could you please share a results of the Slack discussion from Sep 25?
> > > >
> > > > ср, 25 сент. 2019 г. в 15:50, Dmitriy Pavlov :
> > > > >
> > > > > Hi Maxim,
> > > > >
> > > > > Thank you for preparing the release page!
> > > > >
> > > > > Could you please add Require release notes filter? You can find an
> > > example
> > > > > in
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> > > > >
> > > > > Sincerely
> > > > > Dmitriy Pavlov
> > > > >
> > > > > ср, 25 сент. 2019 г. в 11:58, Maxim Muzafarov :
> > > > >
> > > > > > Igniters,
> > > > > >
> > > > > >
> > > > > > It's true that we are still discussing the release dates. But
> > > > > > nevertheless, all the release blockers are important since some
> of
> > > > > > them may require more than one month to be fixed. Let's discuss
> today
> > > > > > how we will handle these issues and track Monitoring and ML major
> > > > > > features to get them into the next release.
> > > > > >
> > > > > > The meeting already scheduled. We will use the ASF Slack on
> Sep