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 wa
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, p
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
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
SqlSystemViewRunn
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%20
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
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 w
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 tha
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 SQ
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
> deli
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:1
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]
12 matches
Mail list logo
