ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9381) p2p does not undeploy ScanQuery IgniteBiPredicate filter on client node disconnect
Date Tue, 25 Sep 2018 08:51:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627023#comment-16627023
] 

Sergey Antonov commented on IGNITE-9381:
----------------------------------------

[~agoncharuk] I made changes in code under your comments.

> 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
>             Fix For: 2.7
>
>         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)

Mime
View raw message