You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Tikhonov (JIRA)" <ji...@apache.org> on 2016/03/17 18:57:33 UTC

[jira] [Commented] (IGNITE-2004) Asynchronous execution of ContinuousQuery's remote filter & local list

    [ https://issues.apache.org/jira/browse/IGNITE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200049#comment-15200049 ] 

Nikolay Tikhonov commented on IGNITE-2004:
------------------------------------------

Added separate thread pool which used for executing callbacks. If a listener and a filter implements marker interface then they will be submitted in non-system thread pool.

> 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)