[
https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162718#comment-16162718
]
Yakov Zhdanov commented on IGNITE-425:
--------------------------------------
[~NIzhikov] [~ntikhonov] [~avinogradov]
Guys, I am a bit concerned with initialQuery() method for new query type. Given
we cannot distinguish newly created entry and one that existed before query is
set up (so we can have the same entry twice - in initial query and in
listener), should we just remove it? If we leave it then, IMO, it should have
the same signature from types standpoint as the query itself.
> Introduce transformers for continuous queries
> ---------------------------------------------
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Reporter: Yakov Zhdanov
> Assignee: Nikolay Izhikov
>
> Currently if updated entry passes the filter, it is sent to node initiated
> the query entirely. It would be good to provide user with the ability to
> transform entry and, for example, select only fields that are important. This
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery<K, V, T> {..} // T is a type transformer
> transforms to
> public ContinuousQuery<K, V, T> setLocalListener(Listener<T> locLsnr) {..} //
> Probably, we will have to introduce new listener type, since user may want to
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery<K, V, T> setRemoteTransformerFactory(Factory<? extends
> ContinuousQueryTransformer<K, V, T>> factory) { ..}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
