[ https://issues.apache.org/jira/browse/IGNITE-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618920#comment-16618920 ]
ASF GitHub Bot commented on IGNITE-9381: ---------------------------------------- GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/4784 IGNITE-9381 fix, reproducer were added You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9381 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4784.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4784 ---- commit 2179d49e9402190016ac33df58dcc6a14c340811 Author: Sergey Antonov <antonovsergey93@...> Date: 2018-09-18T10:44:29Z IGNITE-9381 fix, reproducer were added ---- > 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)