You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Antonov (JIRA)" <ji...@apache.org> on 2018/09/10 13:41:00 UTC
[jira] [Assigned] (IGNITE-9381) p2p does not undeploy ScanQuery
IgniteBiPredicate filter on client node disconnect
[ https://issues.apache.org/jira/browse/IGNITE-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Antonov reassigned IGNITE-9381:
--------------------------------------
Assignee: Sergey Antonov
> p2p does not undeploy ScanQuery IgniteBiPredicate filter on client node disconnect
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-9381
> URL: https://issues.apache.org/jira/browse/IGNITE-9381
> Project: Ignite
> Issue Type: Bug
> Reporter: Andrew Medvedev
> Assignee: Sergey Antonov
> Priority: Major
> Attachments: AndmedScanFilterClassLoadingTest.java, snapshots.xml
>
>
> Once deployed via scan query, an IgniteBiPredicate filter does not change if client reconnects (with a modified filter)
> Steps to reproduce:
> * start server node in separate jvm with attached configuration (persistence enabled)
> * run attached reproducer AndmedScanFilterClassLoadingTest. It includes a task and a scan filter, both print "FOO" on server side
> * modify FOO -> BAR for both
> * re-run modifed AndmedScanFilterClassLoadingTest .
> Expected: Both print "BAR".
> Actual behavior: task prints "BAR", scan filter prints "FOO"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)