Re: How to close/cancel a running tasks?

Hi, To do this you can execute tasks asynchronously(for example, runAsync and others). Async operations return IgniteFuture, which can be canceled. Also, I think that services fit better for this use case - there you can run your code in the background and deploy/undeploy them when a code change

Re: Continuous Query on a varying set of keys

Hello! Yes, using other continuous query to watch changes of this set looks OK. Of course there will be some yak shaving to do. Regards, -- Ilya Kasnacheev вт, 26 мая 2020 г. в 12:28, zork : > Thanks. > So I can think of two ways using which such a set could be maintained by > the > remote

Re: ClientCacheConfiguration with java thin client

Hello, On server-side there is property ExpiryPolicyFactory (not just ExporyPolicy). Factory, in general, can return different expiry policy values for each call, so there is no common way to convert factory class to policy class, except some predefined factory implementations which always return

Re: Continuous Query on a varying set of keys

Hi, Sorry but I could not get it to work. The standard way of defining a remote filter as shown in sample repo is something like: qry.setRemoteFilterFactory(new Factory>() { @Override public CacheEntryEventFilter create() { return new

Re: Continuous Query on a varying set of keys

Hello! No, updating local set will not be sent over to the remote node, but on the remote node you can probably update it from your filter: qry.setRemoteFilterFactory(new Factory>() { @Override public CacheEntryEventFilter create() { return new

Re: Continuous Query on a varying set of keys

Thanks. So I can think of two ways using which such a set could be maintained by the remote node: 1. The remote node listens to a new topic through which the local node sends it a message whenever the set changes. 2. Or, the local node puts the set values in a new table in the cache itself and

Re: ClientCacheConfiguration with java thin client

Thank you so much for reply. I used xml config file for cache Expirypolicy at server node like it is thick client define? what is exactly think client mean? -- Sent

Re: ClientCacheConfiguration with java thin client

Hello, By thick client I mean "not by thin client" (sorry for the confusion), i.e. by client node, by server node, by xml configuration, etc. вт, 26 мая 2020 г. в 12:49, kay : > Thank you so much for reply. > > I used xml config file for cache Expirypolicy at server node > like > > >

Re: ClientCacheConfiguration with java thin client

I see, Thank you so mush :) 나의 iPhone에서 보냄 > 2020. 5. 26. 오후 7:04, Alex Plehanov 작성: > >  > Hello, > > By thick client I mean "not by thin client" (sorry for the confusion), i.e. > by client node, by server node, by xml configuration, etc. > > вт, 26 мая 2020 г. в 12:49, kay : >> Thank

Re: Binary recovery for a very long time

Hi, I enabled debug logging and found the following log output: [2020-05-23T21:43:58,397][DEBUG][nio-acceptor-tcp-comm-#28%ClusterName1%][TcpCommunicationSpi] Balancing data [min0=0, minIdx=0, max0=-1, maxIdx=-1] [2020-05-23T21:43:58,405][DEBUG][main][SchemaManager] Creating DB table with

Re: Change schema on runtime Apache Ignite

When it comes to Ignite schema changes you can always update your POJOs (add or remove fields) on the application end. The cluster will see the change and will work with the new object version without any restarts. Also, if you'd like the schema changes to be visible to Ignite SQL engine you can

Re: Ignite 2.8.0: ConcurrentModificationException on attempt to do put into cache

Hi, looks like there is an error inside ContinousQuery response collection Can you provide more context, and possibly a reproducer project. at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1211)

Re: Ignite cluster node count restriction

Hi, Ignite does not restrict cluster size, but for large deployments > 200 nodes, ZooKeeper discovery is recommended. See: https://apacheignite.readme.io/docs/zookeeper-discovery Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite 2.8.0: ConcurrentModificationException on attempt to do put into cache

Dear Ignite experts, could you please clarify the root cause of the exception below? Ignite Version: 2.8.0 Cache configuration (of the affected cache): ATOMIC, PRIMARY_SYNC, backups=0 Cluster: 4 grid nodes, each 8 cores and 16G heap E 200526 130653.710 [sys-#48] GridTaskWorker - Failed to obtain

Re: Help with possible advanced Ignite questions during a meetup

Hi all, If anyone is interested, here is our approach to Ignite on Google Kubernetes Engine (GKE): https://github.com/doitintl/ignite-gke The slides from my talk are here: https://www.slideshare.net/ZaarHai/apache-ignite-a-doitall-keyvalue-db And the recording is here:

RE: EXT SENDER - Re: Can Tableau Desktop（Windows） connect the database from Apache ignite(Linux)?

Hello: I have installed ODBC driver for apache ignite from Linux ,and create dsn via the ODBC64 in windows , maybe it works , because the Connection Attributes is enabled , so I can configure the Server and port ,but I don't know the database how to configure so that it connect my

Re: Help with possible advanced Ignite questions during a meetup

Dear Denis, Does that mean only "open source/community" version of webconsole will be discontinued? Thanks, Gaurav On Wed, May 27, 2020, 10:32 AM Denis Magda wrote: > Hi Zaar, > > Congratulations and thanks for spreading the word about Ignite in > Australia! I truly liked the style and flow

Re: Help with possible advanced Ignite questions during a meetup

Hi Zaar, Congratulations and thanks for spreading the word about Ignite in Australia! I truly liked the style and flow of your slides. As you reasonably highlighted, Ignite documentation and tooling need more work and attention from the community. Luckily, we are determined to rewrite the docs