Thank you very much Stan
Regards,
Hemasundar
On 23 March 2018 at 19:20, Stanislav Lukyanov
wrote:
> Hi,
>
>
>
> There is an answer for this question already, maybe you didn’t receive it
> - http://apache-ignite-users.70518.x6.nabble.com/Segmentation-policy-
>
Hi,
I am confused about few terms used often in ignite docs. Could someone
please clarify them.
1. What is difference between a Server, JVM and ignite node. Can one have
multiple instances of other 2, like a jvm has two nodes or a node has 2
jvms. Please explain in detail, I am very confused
Hi Val/Denis
Can you please answer this?
Thanks,
prasad
On Sat, Mar 24, 2018, 1:58 PM Prasad Bhalerao
wrote:
> Hi,
> I can't use write through approach. I will be doing CRUD batch operations
> on oracle tables to avoid frequent calls to db.
> Now to keep ignite
Can you clarify what you mean by "real-time query" in this case? Why not just
start node C as a client and run a query from it?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello All,
What is the correct way to cancel a Continuous Query, and make sure all the
resources are used by the query are freed?
I looked in the documentation and the examples, I didn't see any explicit
reference to cancelling a running continuous query.
Thanks,
Andre
--
Sent from:
1. You can call ignite.start() twice in the same JVM, and you get two
Ignite nodes (there are some restrictions around the same cluster I don't
understand). An ignite node may be a client or a server. I believe
can have two client nodes in the same JVM connected to two different
clusters.
Hello Andre,
As mentioned in the javadoc [1], you have to call QueryCursor#close()
method in order to stop receiving updates.
// Create new continuous query.
ContinuousQuery qry = new ContinuousQuery<>();
// Execute query and get cursor that iterates through initial
Thanks Slava!
I had dropped the initial query from my continuous query, so I didn't look
in that direction. You are right it is clearly stated in the docs.
Future reference for others, this works even if the inital query is not
specified.
According to the docs:
/Note that this works even
This makes sense, and actually that's exactly how initialQuery works. It's
executed after continuous query listener is deployed, so nothing is missed,
but duplicates are possible.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Naveen,
Ignite does not provide such integration out of the box, however there a
commercial offering from GridGain for that:
https://docs.gridgain.com/docs/goldengate-replication
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Scott,
With eagetTTL=false, each time you access an entry its TTL is automatically
checked - if it is expired, the entry will be removed. It means that instead
of having a separate thread waking up and removing all of the expired
entries at the same time (and taking a chunk of CPU and IO for a
Hm.. Not sore what happened exactly in your case, but cache store is never
deployed via peer class loading. It's required that you have a class
explicitly deployed on every node prior to start up.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Never heard of anyone doing this, but I don't see why it wouldn't work. Did
you have any issues while working with this combination?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
There is no native graph support in Ignite. However, for certain use cases it
might be possible to store graph data in a set of caches, and then use
compute APIs [1] to do the processing.
[1] https://apacheignite.readme.io/docs/compute-grid
-Val
--
Sent from:
Maybe beause there is no callback fucntion for
org.apache.ignite.IgniteJdbcThinDriver.
I use a class mock liquibase, hope can help you:
/*
* To change this license header, choose License Headers in Project Properties.
* To change this template file, choose Tools | Templates
* and open
15 matches
Mail list logo