ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (IGNITE-425) Introduce transformers for continuous queries
Date Tue, 30 Jan 2018 16:40:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anton Vinogradov updated IGNITE-425:
------------------------------------
    Comment: was deleted

(was: [~NIzhikov], 

Bench should be refactored

1) We should wait for event/ We interested in time between put and event)

> 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
>    Affects Versions: 2.2
>            Reporter: Yakov Zhdanov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>             Fix For: 2.5
>
>
> 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
(v7.6.3#76005)

Mime
View raw message