[
https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152585#comment-16152585
]
Nikolay Izhikov commented on IGNITE-425:
----------------------------------------
Hello, [~ntikhonov]
I discuss changes with community
http://apache-ignite-developers.2346864.n4.nabble.com/ContinuousQueryWithTransformer-implementation-questions-2-td21418.html#a21673
Decisions:
# Introduce base class for ContinuousQuery to prevent code duplication -
\[DONE\]
# Keep current implementation of exception handling
## filter exception treats as `true`
## transformer exception treats as `null`
# Start another dev-list discussion to make exception handling clear both in
regular ContinuousQuery and in ContinuousQueryWithTransformer.
Can you continue reviewing my PR?
Should I merge my PR with lates master?
> 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)
