ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1191) Continuous Query Changes
Date Mon, 17 Aug 2015 05:59:45 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699049#comment-14699049
] 

Vladimir Ozerov commented on IGNITE-1191:
-----------------------------------------

My several comments:
1) In this design we extend MutableCacheEntryListenerConfiguration class. This seems a bit
dangerous for me because it is a) serializable; b) out of our control. Should jcache specification
change in a non-compatible way (e.g. another field is added/removed), we will end up in broken
compatibility between Ignite versions. May be it is better to implement CacheEntryListenerConfiguration
instead? This will require a bit more LOCs, but will be much safer.
2) In old good GridGain days we already have a kind of flag "initialIteration". Later on we
removed it in favor of optional *query*. Now you propose switching back to a boolean flag
again. What is the reason for this? I'm not a fan of "initial queries" and think they are
useless, but still - boolean flag is less flexible approach than query.

> Continuous Query Changes
> ------------------------
>
>                 Key: IGNITE-1191
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1191
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Dmitriy Setrakyan
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message