[
https://issues.apache.org/jira/browse/IGNITE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058261#comment-15058261
]
Andrey Kornev commented on IGNITE-2004:
---------------------------------------
Just wanted to clarify that the same limitation applies for the query listeners
(unless the term "filter" here is used loosely to also include the listeners):
they are invoked synchronously by the same thread that has caused the cache
event.
The JCache's cache listener functionality suffers from the same problem since
it's implemented on top the CQ feature. Also,
CacheEntryListenerConfiguration.isSynchronous() property is not respected by
the current implementation: the listeners are invoked synchronously regardless
of the value of the property.
> Asynchronous execution of ContinuousQuery's remote filter
> ---------------------------------------------------------
>
> 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: Valentin Kulichenko
> 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)
