[
https://issues.apache.org/jira/browse/IGNITE-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653490#comment-16653490
]
ASF GitHub Bot commented on IGNITE-9899:
----------------------------------------
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/5011
IGNITE-9899 Fix processing of TX cache backups by continuous queries.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9899
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5011.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5011
----
commit 32ff0f95e4e93ee07037f6f9b4d071c344530b5f
Author: Denis Mekhanikov <dmekhanikov@...>
Date: 2018-10-17T12:32:13Z
IGNITE-9899 Fix processing of TX cache backups by continuous queries.
----
> Continuous query handlers are not called on backups when one-phase commit is
> used
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-9899
> URL: https://issues.apache.org/jira/browse/IGNITE-9899
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Denis Mekhanikov
> Assignee: Denis Mekhanikov
> Priority: Major
> Attachments: CacheContinuousQueryTxBackupTest.java
>
>
> Consider the following cache configuration:
> * Atomicity mode: Transactional
> * Cache mode: Partitioned
> * Backups: 1
> If a continuous query is registered for such cache, then it's not processed
> on backup copies. It results in remote filters not being called on backups
> and lost events on changing topology.
> Test case is attached: [^CacheContinuousQueryTxBackupTest.java]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
