Just to add one more finding.
If I execute my query in one piece, runtime is 10 to 15 seconds (for
updating 1252 rows)
UPDATE PUBLIC.AAA_STR_HIE_ACCOUNT
SET MBR_TYPE = 'B'
WHERE ID IN (
SELECT DISTINCT t1.ID
FROM PUBLIC.AAA_STR_HIE_ACCOUNT t1
LEFT JOIN PUBLIC.AAA_STR_HIE_ACCOUNT t2 ON
Hello,
I am using Ignite 2.7 embedded inside a Tomcat application, and have run
into an issue where the application does not shut down due to a blocked
Ignite thread. I think it would be good for Ignite to avoid hanging in this
situation, what do you think? Here are the details:
1. Ignite node
Hi,
Is it possible to configure a custom IndexingSpi per cache? I'd like to have
a custom indexing mechanism to improve the full text capabilities but I
would like to enable only in some caches. is that possible? Is it possible
to configure multiple indexingSpi?
Adding a custom indexingspi to
Ilya, could you please share more details on why it works this way. It will
be useful to know.
-
Denis
On Mon, May 27, 2019 at 6:53 AM Ilya Kasnacheev
wrote:
> Hello!
>
> > How the system is supposed to free disk space?
>
> It's not supposed to!
>
> Ignite does not make effort to return disk
Hi,
Cache.destroy() completely removes caches from all the nodes in the
cluster, while Cache.close() just closes the local proxy for the cache. So,
yes, data will be lost in case of invoking destroy from the client node.
Evgenii
пн, 10 июн. 2019 г. в 19:23, foobar2 :
> Hello. I am using Ignite
Hello. I am using Ignite Cache in scala app. The node I use is in client
mode. After reading the documentation and testing it's still unclear for me
what is the difference of between destroy and close on the non-local cache
from client node? Basically, I want to know is can I possibly lose the
Hi, is there a plan to implement this (join on UPDATE) or to improve the
performance of the "IN" operator ?
I have an UPDATE query with two "IN" operators.
UPDATE PUBLIC.AAA_STR_HIE_ACCOUNT
SET MBR_TYPE = 'B'
WHERE ID IN (
SELECT ID
...'
Hi, I have a SpringBoot's application 2.1.X and a simple local installation of
ignite 2.7.0.
I have problems when I add to my Repository two simple query methods (without
this methods I don't have problems, the simple call to "repo.findById" works
correctly ) like this:
Hello!
As a rule, a faulty thick client can destabilize a cluster. Ignite's
architecture assumes that all clients are collocated, i.e. that the network
between any two nodes (including clients) is reliable, fast and low-latency.
It is not recommended to connect thick clients from different
