Dmitry,
There is a ticket for this enhancement:
https://issues.apache.org/jira/browse/IGNITE-7285
-Val
On Sat, Jan 13, 2018 at 6:16 PM, Dmitriy Setrakyan
wrote:
> Forwarding to the dev list.
>
> Can anyone comment on why we do not have a default query timeout? This
> should be very simple to a
Cross sending to dev@.
Can anyone from committers review this patch? It is scheduled for 2.4 and
there is not much time left.
D.
-- Forwarded message --
From: Sergey Sergeev
Date: Tue, Jan 2, 2018 at 7:02 AM
Subject: Re: Page eviction mode is ignored
To: u...@ignite.apache.org
Cross-sending this to dev@.
Alexey Goncharuk, you are probably the best person to help here. The
problem the user is having looks like a serious usability issue. Do you
have any ideas on how to improve the current behavior?
D.
-- Forwarded message --
From: Ilya Kasnacheev
Date:
Cross-sending to dev@.
Alexey,
This issue is marked to be fixed for 2.4 which is planned to be released in
a couple of weeks. Do you think you will be able to close this issue before
the release?
D.
On Mon, Dec 18, 2017 at 9:51 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Creat
Forwarding to the dev list.
Can anyone comment on why we do not have a default query timeout? This
should be very simple to add.
D.
-- Forwarded message --
From: afedotov
Date: Thu, Dec 14, 2017 at 10:12 AM
Subject: Re: how to set SQL timeout for the cluster?
To: u...@ignite.apa
Denis, we have "setNodeAttributes(...)" [1] method on TCP discovery SPI. I
believe it may be used to provide which attributes to include during the
node-join process. Can you please take a look?
[1]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoveryS
Igniters, as most of you are aware, Apache Ignite supports a range of different
Application Programming Interfaces (APIs). Akmal Chaudhri just published the
first in a multi-part series offering a detailed look at how Apache Ignite
manages transactions in its key-value API and some of the mechan
