[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-4918: Fix Version/s: (was: 2.10) > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrey Mashenkov >Priority: Major > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-4918: -- Fix Version/s: (was: 2.9) 2.10 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrey Mashenkov >Priority: Major > Fix For: 2.10 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-4918: Fix Version/s: (was: 2.8) 2.9 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrey Mashenkov >Priority: Major > Fix For: 2.9 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Fix Version/s: (was: 2.7) 2.8 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov >Priority: Major > Fix For: 2.8 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-4918: --- Fix Version/s: (was: 2.6) 2.7 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov >Priority: Major > Fix For: 2.7 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-4918: Fix Version/s: (was: 2.5) 2.6 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov >Priority: Major > Fix For: 2.6 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4918: Fix Version/s: (was: 2.4) 2.5 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov >Priority: Major > Fix For: 2.5 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Fix Version/s: (was: 2.3) 2.4 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov > Fix For: 2.4 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Fix Version/s: (was: 2.1) 2.2 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov > Fix For: 2.2 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Fix Version/s: (was: 2.0) 2.1 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov > Fix For: 2.1 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Description: PFA reproducer attached. Peer class loading should be enabled on both, server and client. Server should NOT has scan query filter class in its classpath. Steps to reproduce: - start standalone server - run repro, it should work fine. - run repro with changed filter code, it will return same results as on previous step. Looks like filter code is cached on server and is never being updated. was: PFA reproducer attached. Peer class loading should be enabled on both, server and client. Server should NOT has scan query filter class in its classpath. Steps to reproduce: - start standalone server - run repro, it should work fine. - run repro with changed filter code, it will return same results. > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov > Fix For: 2.0 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results as on > previous step. > Looks like filter code is cached on server and is never being updated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Fix Version/s: 2.0 > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov > Fix For: 2.0 > > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Description: PFA reproducer attached. Peer class loading should be enabled on both, server and client. Server should NOT has scan query filter class in its classpath. Steps to reproduce: - start standalone server - run repro, it should work fine. - run repro with changed filter code, it will return same results. was: PFA reproducer attached. Steps to reproduce: - start standalone server - run repro, it should work fine. - run repro with changed filter code, it will return same results. > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. Peer class loading should be enabled on both, server > and client. > Server should NOT has scan query filter class in its classpath. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Description: PFA reproducer attached. Steps to reproduce: - start standalone server - run repro, it should work fine. - run repro with changed filter code, it will return same results. > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4918) ScanQuery filter class code is not updated on server once it has been changed on client.
[ https://issues.apache.org/jira/browse/IGNITE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4918: - Attachment: ScanQueryFilter.java > ScanQuery filter class code is not updated on server once it has been changed > on client. > > > Key: IGNITE-4918 > URL: https://issues.apache.org/jira/browse/IGNITE-4918 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.9 >Reporter: Andrew Mashenkov > Attachments: ScanQueryFilter.java > > > PFA reproducer attached. > Steps to reproduce: > - start standalone server > - run repro, it should work fine. > - run repro with changed filter code, it will return same results. -- This message was sent by Atlassian JIRA (v6.3.15#6346)