ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-1186) Filter is sent instead of factory when continuous query is created
Date Mon, 03 Aug 2015 23:09:04 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitriy Setrakyan updated IGNITE-1186:
--------------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: IGNITE-1191

> 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: Sub-task
>          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)

Mime
View raw message