ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nikolay Tikhonov <ntikho...@gridgain.com>
Subject Re: Why the Continuous Queries ignore expired event permanently?
Date Thu, 07 Jul 2016 05:21:19 GMT
Hi Lin,

CQ doesn't support expired events by historical reason. But you can use
CacheEntryListener [1] which support the same functionality that CQ and
allow to get expired events [2].

[1] IgniteCache#registerCacheEntryListener
[2] javax.cache.event.CacheEntryExpiredListener

On Wed, Jul 6, 2016 at 7:14 PM, Denis Magda <dmagda@gridgain.com> wrote:

> Hi Lin,
>
> As far as I recall this kind of events are not supported by CQ (continuous
> queries) right know. However I’m not sure about the reason.
>
> *Nick*, can you comment this?
>
> —
> Denis
>
> On Jul 6, 2016, at 10:17 AM, Lin <me@linlyu.com> wrote:
>
> Hi all,
>
> I am trying to switch my event listener application from event subsystem
> with CacheEvent to the Continuous Queries with CacheEntryEvent, and I found
> that the system will ignore all the expired events.
>
> Please see the code
> in org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager#executeQuery
> and
>
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryListener#onEntryUpdated.
>
> No matter CacheContinuousQueryHandlerV2 or CacheContinuousQueryHandler,
> the parameter of ignoreExpired is always true.
>
> 1. What do you consider to ignore expired events?
> 2. What if I set the parameter ignoreExpired to false?
>
>
> Regards,
>
> Lin.
>
>
>

Mime
View raw message