[
https://issues.apache.org/jira/browse/IGNITE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237091#comment-15237091
]
Semen Boikov edited comment on IGNITE-2004 at 4/12/16 1:02 PM:
---------------------------------------------------------------
Reviewed, my comments:
- please add failover test with async mode
- please add test using JCache API + async listener/filter
- please get rid of unnecessary calls of 'updateListeners' in GridDhtAtomicCache
- when I change number of threads to 20 in
CacheContinuousQueryOperationFromCallbackTest then test fails to wait for some
events, please check if this is test issue or cache bug (I want to change test
to use 'IgniteConfiguration.systemThreadPoolSize * 2' threads)
was (Author: sboikov):
Reviewed, my comments:
- please add failover test with async mode
- please add test using JCache API + async listener/filter
- please get rid of unnecessary calls of 'updateListeners' in GridDhtAtomicCache
> 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)
