ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node
Date Fri, 15 Jan 2016 08:32:39 GMT

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

Alexey Goncharuk closed IGNITE-2032.

> Filters passed to ScanQuery are not redeployed when originating from a client node
> ----------------------------------------------------------------------------------
>                 Key: IGNITE-2032
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2032
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>            Assignee: Alexey Goncharuk
>            Priority: Critical
>              Labels: important
>             Fix For: 1.6
>         Attachments: ScanQueryFailure.java, test-config.xml
> The following case doesn't work:
> - start a standalone server node with peer class loading enabled;
> - start a client node, populate a cache with data, perform a scan query using a filter;
> - since the server doesn't have the filter in its classpath it will load it from the
client. Everything works fine here;
> - stop the client, the server will undeploy the filter. No issue here so far;
> - modify the filter a bit and start the client one more time. The server won't deploy
the new version of the filter and will be using the old regardless of the fact that it was
undeployed before according to the logs.
> The server can be started using ignite.bat and test-config.xml (attached).
> The source of the client is located in attached ScanQueryFailure.java.
> BTW, everything works fine if to use the server mode instead of the client one.

This message was sent by Atlassian JIRA

View raw message