You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by "aaron@tophold.com" <aa...@tophold.com> on 2017/09/05 11:26:11 UTC
Is there any way to listener to a specific remote cache's update events ?
hi All,
I look around the event section try to find a way to catch a specific cache's update events, and persist those event to a historical database.
We have a instance update a market data Ignite cache; on another side we need persist all those historical events.
The listener side host in a standalone machine, it does not care data in cache only the updates.
we try several ways, local or remote but seem only the cache data node got the events, while the remote not;
also this cache data node may have multiple caches. while we only want monitor one of them,
Another way we try to define a specific topic and manually trigger a publish event, seem can work.
Thanks for your time!
Regards
Aaron
aaron@tophold.com
Re: Re: Is there any way to listener to a specific remote cache's update events ?
Posted by "aaron@tophold.com" <aa...@tophold.com>.
yes, this can work, still one small question:
My cache is partition , so we start this continuous query on each partition nodes as locally #setLocal(true).
From the java doc, the init query will hit only the local node, will update listener be trigger only local node update happen?
As we do not want any update events pass cross nodes, so that handing in local node suppose be much quicker.
Thanks for your time!
Regards
Aaron
aaron@tophold.com
From: aaron@tophold.com
Date: 2017-09-05 20:46
To: user
Subject: Re: Re: Is there any way to listener to a specific remote cache's update events ?
Great, thanks this seem what we need, we will have a try, thanks you Nikolay!
Regards
Aaron
aaron@tophold.com
From: Nikolay Izhikov
Date: 2017-09-05 19:38
To: user
Subject: Re: Is there any way to listener to a specific remote cache's update events ?
Hello, Aaron.
I think continuous query is what you need:
https://apacheignite.readme.io/docs/continuous-queries#section-local-listener
You can also use Ignite as jcache implementation and register jcache
listener on IgniteCache:
https://static.javadoc.io/javax.cache/cache-api/1.0.0/javax/cache/Cache.html#registerCacheEntryListener(javax.cache.configuration.CacheEntryListenerConfiguration)
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html
05.09.2017 14:26, aaron@tophold.com пишет:
> hi All,
>
> I look around the event section try to find a way to catch a specific
> cache's update events, and persist those event to a historical database.
>
> We have a instance update a market data Ignite cache; on another side we
> need persist all those historical events.
>
> The listener side host in a standalone machine, it does not care data in
> cache only the updates.
>
> we try several ways, local or remote but seem only the cache data node
> got the events, while the remote not;
>
> also this cache data node may have multiple caches. while we only want
> monitor one of them,
>
> Another way we try to define a specific topic and manually trigger a
> publish event, seem can work.
>
> Thanks for your time!
>
> Regards
> Aaron
> ------------------------------------------------------------------------
> aaron@tophold.com
Re: Re: Is there any way to listener to a specific remote cache's update events ?
Posted by "aaron@tophold.com" <aa...@tophold.com>.
Great, thanks this seem what we need, we will have a try, thanks you Nikolay!
Regards
Aaron
aaron@tophold.com
From: Nikolay Izhikov
Date: 2017-09-05 19:38
To: user
Subject: Re: Is there any way to listener to a specific remote cache's update events ?
Hello, Aaron.
I think continuous query is what you need:
https://apacheignite.readme.io/docs/continuous-queries#section-local-listener
You can also use Ignite as jcache implementation and register jcache
listener on IgniteCache:
https://static.javadoc.io/javax.cache/cache-api/1.0.0/javax/cache/Cache.html#registerCacheEntryListener(javax.cache.configuration.CacheEntryListenerConfiguration)
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html
05.09.2017 14:26, aaron@tophold.com пишет:
> hi All,
>
> I look around the event section try to find a way to catch a specific
> cache's update events, and persist those event to a historical database.
>
> We have a instance update a market data Ignite cache; on another side we
> need persist all those historical events.
>
> The listener side host in a standalone machine, it does not care data in
> cache only the updates.
>
> we try several ways, local or remote but seem only the cache data node
> got the events, while the remote not;
>
> also this cache data node may have multiple caches. while we only want
> monitor one of them,
>
> Another way we try to define a specific topic and manually trigger a
> publish event, seem can work.
>
> Thanks for your time!
>
> Regards
> Aaron
> ------------------------------------------------------------------------
> aaron@tophold.com
Re: Is there any way to listener to a specific remote cache's update
events ?
Posted by Nikolay Izhikov <ni...@gmail.com>.
Hello, Aaron.
I think continuous query is what you need:
https://apacheignite.readme.io/docs/continuous-queries#section-local-listener
You can also use Ignite as jcache implementation and register jcache
listener on IgniteCache:
https://static.javadoc.io/javax.cache/cache-api/1.0.0/javax/cache/Cache.html#registerCacheEntryListener(javax.cache.configuration.CacheEntryListenerConfiguration)
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html
05.09.2017 14:26, aaron@tophold.com пишет:
> hi All,
>
> I look around the event section try to find a way to catch a specific
> cache's update events, and persist those event to a historical database.
>
> We have a instance update a market data Ignite cache; on another side we
> need persist all those historical events.
>
> The listener side host in a standalone machine, it does not care data in
> cache only the updates.
>
> we try several ways, local or remote but seem only the cache data node
> got the events, while the remote not;
>
> also this cache data node may have multiple caches. while we only want
> monitor one of them,
>
> Another way we try to define a specific topic and manually trigger a
> publish event, seem can work.
>
> Thanks for your time!
>
> Regards
> Aaron
> ------------------------------------------------------------------------
> aaron@tophold.com