You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/03/21 10:53:25 UTC
[jira] [Created] (IGNITE-2865) Continuous query event passed to
filter should be immutable for users.
Vladimir Ozerov created IGNITE-2865:
---------------------------------------
Summary: Continuous query event passed to filter should be immutable for users.
Key: IGNITE-2865
URL: https://issues.apache.org/jira/browse/IGNITE-2865
Project: Ignite
Issue Type: Task
Components: cache
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Priority: Critical
Fix For: 1.6
*Problem*
When event is passed to continuous query filter, it can be used only in scope of this method. The reason is that if filter returns {{false}}, the method {{CacheContinuousQueryEntry.markFiltered()}} is called. This method *clears* key and values.
*Solution*
We should not clear key and values. Instead, we should properly check for {{FILTERED_ENTRY}} flag in all methods where {{key/newVal/oldVal/depInfo}} are used. This includes generated {{readFrom()/writeTo()}} methods as well - their manual change will be required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)