[
https://issues.apache.org/jira/browse/IGNITE-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399658#comment-15399658
]
Ross Anderson commented on IGNITE-3607:
---------------------------------------
If a continuous query is given an ID, then the IDs of the queries where the
update passed the remote filter could be sent alongside the update from the
server.
This way the Client could propagate the update to the appropriate listeners -
all the null listeners, and all the listeners with IDs matching those provided
by the server on the update.
This would allow a single message per client regardless of the type of filters
(i.e. they do not have to be null).
> Send non-filtered continuous query notifications in one message per client
> --------------------------------------------------------------------------
>
> Key: IGNITE-3607
> URL: https://issues.apache.org/jira/browse/IGNITE-3607
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.4
> Reporter: Alexey Goncharuk
>
> If a client subscribes N continuous queries to a cache, Ignite will send
> individual notifications for each of the updates. We can send notifications
> for all queries with null filter in one message per client.
> See
> http://apache-ignite-users.70518.x6.nabble.com/Deadlock-during-Client-Continuous-Query-deserialization-td6565.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
