You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Jason Man (JIRA)" <ji...@apache.org> on 2016/09/28 01:47:20 UTC
[jira] [Updated] (IGNITE-3984) NullPointerException in
IgniteCacheProxy when creating continuous query
[ https://issues.apache.org/jira/browse/IGNITE-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Man updated IGNITE-3984:
------------------------------
Attachment: ContQueryTest.java
> NullPointerException in IgniteCacheProxy when creating continuous query
> -----------------------------------------------------------------------
>
> Key: IGNITE-3984
> URL: https://issues.apache.org/jira/browse/IGNITE-3984
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.7
> Reporter: Jason Man
> Attachments: ContQueryTest.java
>
>
> Test attached. This used to work fine in 1.6. This seem to be related to this jira and PR:
> https://issues.apache.org/jira/browse/IGNITE-3413
> https://github.com/apache/ignite/commit/89d64e74b697054a88c3a91433aaaf4f7fdd0284
> Here's the scenario:
> * First node starts with special attribute and creates a cache with the node filter that allows to deploy it only on nodes with this attribute
> * Second node starts without the attribute is started. When creating a continuous query to query the cache created by the first node, a NullPointerException is thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)