[
https://issues.apache.org/jira/browse/IGNITE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240660#comment-15240660
]
Semen Boikov commented on IGNITE-2004:
--------------------------------------
Hi,
I did few very minor changes, please take a look. Please fix javadoc for
IgniteAsyncCallback (statement about pools) and for ContinuousQuery
(IgniteAsyncCallback is not an interface).
Also please make 'CacheContinuousQueryHandler.notifyCallback' more optimal: do
not create any additional collections if all entries are for the same parition.
Also I think Collection in this method is always List, so it is possible to
avoid iterator creation.
> Asynchronous execution of ContinuousQuery's remote filter & local list
> ----------------------------------------------------------------------
>
> Key: IGNITE-2004
> URL: https://issues.apache.org/jira/browse/IGNITE-2004
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: ignite-1.4
> Reporter: Denis Magda
> Assignee: Nikolay Tikhonov
> Labels: important
> Fix For: 1.6
>
>
> Presently remote filters are executed synchronously an entry update. This
> leads to the limitation when it's disallowed to perform cache related
> operation in a filter body.
> It's required to add the ability to execute remote filters asynchronously.
> This will let to execute any kind of operations including cache operations
> directly in the filter body.
> The solution must be fault-tolerant. At least once execution of a filter in
> case of a failure works fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
