Hi,
It shouldn't work like you described:
Continuous query clients should only be receiving the records that are
pertinent to their filters/transformers.
verify the continuous query definitions using the appropriate view:
https://apacheignite.readme.io/docs/continuous_queries
take a look
Hi,
as for fat jar: https://www.baeldung.com/executable-jar-with-maven
But it's not necessary to create a fat jar, you can just put all needed
libraries to the lib folder and add these libs to the classpath when you
start jar:
https://docs.oracle.com/javase/7/docs/technotes/tools/windows/classpat
Hi
I am new to JAVA. If possible , can you please share a link on how to
create fat jar(i.e jar with all dependencies) using eclipse.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ok cool!
On Thu, 7 May 2020 at 13:46, Evgenii Zhuravlev
wrote:
> It's not changing the default Expiry Policy, you will have a new Expiry
> Policy as long as you use this "cache" object. withExpiryPolivy return
> proxy with a new policy, so, all objects that were inserted using this
> "cache" obj
It's not changing the default Expiry Policy, you will have a new Expiry
Policy as long as you use this "cache" object. withExpiryPolivy return
proxy with a new policy, so, all objects that were inserted using this
"cache" object, will have a new policy.
Evgenii
чт, 7 мая 2020 г. в 10:39, John Smi
Ok cool. I create my cache using a template and the rest API, but when I
start my application I do...
cache = this.ignite.cache(this.cacheName)
.withExpiryPolicy(new ModifiedExpiryPolicy(new
Duration(timeUnit, this.cacheTtlDuration)));
Can it be changed then at startup as am doing above?
Hi,
There is no way to change the default policy for the already created cache.
The expiry policy can be changed for all operations on one cache proxy
object using withExpiryPolicy.
Evgenii
чт, 7 мая 2020 г. в 09:46, John Smith :
> Hi running 2.7.0
>
> I created a cache with ModifiedExpiryPolic
Hi,
It looks like the third server node was not a part of this cluster before
restart. Can you share full logs from all server nodes?
Evgenii
чт, 7 мая 2020 г. в 09:11, John Smith :
> Hi, running 2.7.0 on 3 deployed on VMs running Ubuntu.
>
> I checked the state of the cluster by going to: /ign
Hi running 2.7.0
I created a cache with ModifiedExpiryPolicy
Can we change the policy of the created cache? I know we can do per write
but can we change the default of the existing cache to another policy?
Hi, running 2.7.0 on 3 deployed on VMs running Ubuntu.
I checked the state of the cluster by going to: /ignite?cmd=currentState
And the response was:
{"successStatus":0,"error":null,"sessionToken":null,"response":true}
I also checked: /ignite?cmd=size&cacheName=
2 nodes where reporting 3 mill
The Apache Ignite Community is pleased to announce the release of
Apache Ignite Spring Boot extensions 1.0.0
Apache Ignite [1] is a memory-centric distributed database, caching,
and processing platform for transactional, analytical, and streaming
workloads delivering in-memory speeds at petabyte s
Here's the video: https://youtu.be/TCsl-W0tsEE
вт, 28 апр. 2020 г. в 20:48, Ivan Rakov :
> Hi,
>
> Tomorrow (Apr 29) I'll present a webinar [1] on basic data safety /
> consistency guarantees that can be provided by Ignite. We'll discuss data
> replication modes, atomic / TX caches, write sync mo
Hello!
1) Are you sure that your DELETE actually gets to run?
2) I think you need to stop SELECT iteration before running more queries,
including DELETE. Try closing cursor explicitly.
Regards,
--
Ilya Kasnacheev
вт, 5 мая 2020 г. в 11:12, Jueverhard :
> Ok, I think the problem comes from raw
We have about 5 clients. Each client starts 2 different CQ to the same cache
abc . (We need 2 CQ since we want different action and different lifecycle
when the local listener is triggered for either query. )
Client 1 :
Say CQ1 is listening to changes to a record where name is name1. (There is a
14 matches
Mail list logo
