Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Date: Fri, 31 Jul 2015 19:23:04 +0000 (UTC)
From: "Valentin Kulichenko (JIRA)" <jira@apache.org>
To: dev@ignite.incubator.apache.org
Message-ID: <JIRA.12850687.1438370569000.342894.1438370584592@Atlassian.JIRA>
In-Reply-To: <JIRA.12850687.1438370569000@Atlassian.JIRA>
References: <JIRA.12850687.1438370569000@Atlassian.JIRA>
 <JIRA.12850687.1438370569423@arcas>
Subject: [jira] [Created] (IGNITE-1186) Filter is sent instead of factory
 when continuous query is created
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Valentin Kulichenko created IGNITE-1186:
-------------------------------------------

             Summary: Filter is sent instead of factory when continuous query is created
                 Key: IGNITE-1186
                 URL: https://issues.apache.org/jira/browse/IGNITE-1186
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: 1.1.4
            Reporter: Valentin Kulichenko
            Priority: Critical


{{CacheContinuousQueryHandler}}, which is sent to remote nodes on query creation always contains {{CacheEntryEventSerializableFilter}}. This is OK for our {{ContinuousQuery}} API, because it doesn't work with factories, but not OK for JCache entry listener API. {{CacheEntryListenerConfiguration}} contains factory and it's assumed that the filter is created on remote node and is never sent through network. But we require the filter to be {{Serializable}}.

We need to always send factory instead of the filter. In case of {{ContinuousQuery}} API we can use singleton factory that will wrap the instance that already exist.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)