[
https://issues.apache.org/jira/browse/IGNITE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215806#comment-15215806
]
Semen Boikov commented on IGNITE-2004:
--------------------------------------
Reviewed, have some comments:
- the major issue is that if filter is asynchronous then notification code
should be called from the same thread which execute filter, otherwise in
current implementation starvation is possible
- please add tests verifying call order filter and listener
- CacheContinuousQueryAsyncFilterListenerTest should really fail if lsitener
and filter are not async
- in CacheContinuousQueryAsyncFilterListenerTest pelase add check that
continous query event for operation executed from listener/fitler is recevied
> 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)
