[
https://issues.apache.org/jira/browse/IGNITE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022325#comment-15022325
]
ASF GitHub Bot commented on IGNITE-1983:
----------------------------------------
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/255
IGNITE-1983 .Net: Continuous query tests fail
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1983-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/255.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 #255
----
commit 9c113de8a0895a3dac774c81229d33a4a5ab6aaf
Author: Pavel Tupitsyn <[email protected]>
Date: 2015-11-23T15:50:00Z
IGNITE-1983 .Net: Continuous query tests fail
----
> .Net: Continuous query tests fail
> ---------------------------------
>
> Key: IGNITE-1983
> URL: https://issues.apache.org/jira/browse/IGNITE-1983
> Project: Ignite
> Issue Type: Bug
> Components: interop
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Blocker
> Fix For: 1.5
>
>
> See ContinuousQueryAtomiclBackupTest:
> * ContinuousQueryAbstractTest.TestFilterBinarizable
> * ContinuousQueryAbstractTest.TestFilterSerializable
> * ContinuousQueryAbstractTest.TestKeepBinary
> Logic has changed: now there is a continuous query filter call on each node
> (primary and backups), instead of a single event on a primary node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
