[
https://issues.apache.org/jira/browse/IGNITE-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385427#comment-15385427
]
Denis Magda commented on IGNITE-3470:
-------------------------------------
[~ntikhonov], is feasible to support {{updateCounter}} for expired events from
design point of view?
Presently it's ignored if to look at this code line
{code}
// Initial query entry or evicted entry. These events should be fired
immediately.
if (e.updateCounter() == -1L) {
return !e.isFiltered() ? F.<CacheEntryEvent<? extends K, ? extends
V>>asList(
new CacheContinuousQueryEvent<K, V>(cache, cctx, e)) :
Collections.<CacheEntryEvent<? extends K, ? extends
V>>emptyList();
{code}
> Continuous queries should support EXPIRED events
> ------------------------------------------------
>
> Key: IGNITE-3470
> URL: https://issues.apache.org/jira/browse/IGNITE-3470
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 1.6
> Reporter: Valentin Kulichenko
> Assignee: Valentin Kulichenko
> Fix For: 1.7
>
>
> {{EXPIRED}} events are supported in JCache event listeners, but are ignored
> in continuous queries. We should support them there as well.
> Not to confuse existing users, I think we should make listening to
> {{EXPIRED}} events optional and add {{includeExpired}} property to
> {{ContinuousQuery}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
