Mike, First of all, it's recommended to have a separate cache per table to avoid storing of objects of different types in the same cache.
Continuous query receives all updates on the cache regardless of their type. Local listener is invoked when new events happen. Existing records can be processed using initial query. Refer to the following documentation page for more information: https://apacheignite.readme.io/docs/continuous-queries Denis чт, 2 мая 2019 г. в 14:14, Mike Needham <[email protected]>: > I have seen that example, what I do not understand is I have two SQL > tables in a cache that has n number of nodes. it is loaded ahead of time > and a client wants to be notified when the contents of the cache are > changed. Do you have to have the continuous query in a never ending loop > to not have it end? All the examples are simply using ContinuousQuery< > Integer, String>. my example uses <Long, Exchange.class> which is a java > class defining the structure. do I just set-up a ContinuousQuery<Long, > Exchange.class> > > On Thu, May 2, 2019 at 3:59 AM aealexsandrov <[email protected]> > wrote: > >> Hi, >> >> The good example of how it can be done you can see here: >> >> >> https://github.com/gridgain/gridgain-advanced-examples/blob/master/src/main/java/org/gridgain/examples/datagrid/query/ContinuousQueryExample.java >> >> You can set remote listener to handle changes on remote nodes and local >> listers for current. >> >> Note that you will get the updates only until ContinuousQuery will not be >> closed or until the node that starts it will not left the cluster. >> >> Also, you can try to use CacheEvents like in example here: >> >> https://apacheignite.readme.io/docs/events#section-remote-events >> >> Note that events can affect your performance. >> >> BR, >> Andrei >> >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> > > > -- > *Don't be afraid to be wrong. Don't be afraid to admit you don't have all > the answers. Don't be afraid to say "I think" instead of "I know."* >
