[
https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174504#comment-16174504
]
Nikolay Izhikov edited comment on IGNITE-425 at 9/21/17 9:57 AM:
-----------------------------------------------------------------
TC run on pull request merged with latest master -
https://ci.ignite.apache.org/viewLog.html?buildId=843081
actual upsource review -
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-347
was (Author: nizhikov):
TC run on pull request merged with latest master -
https://ci.ignite.apache.org/viewLog.html?buildId=843081
> 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)
