ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "tonysze (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.
Date Thu, 04 Jan 2018 05:33:00 GMT

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

tonysze commented on IGNITE-3653:

In Ignite 2.3.0, I have added the following line in org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.register
(line number 317):

        p2pUnmarshal(ctx.localNodeId(), ctx);

Just before:

        final CacheEntryEventFilter filter = getEventFilter();

Afterward, the RemoteFilter can be loaded, *PROVIDED* that the RemoteFilterFactory class is
already available on the Server node. Continuous Query also seems working and can fail over
between server nodes.

If the RemoteFilterFactory class is not available on the server node, there would be another
exception. Also, I haven't ran the full set of test cases yet, so not sure if it may introduce
other problems.

> P2P doesn't work for remote filter and filter factory.
> ------------------------------------------------------
>                 Key: IGNITE-3653
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3653
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.6
>            Reporter: Nikolay Tikhonov
>         Attachments: CCP2PTest.patch
> Remote filter and filter factory classes were not deployed on nodes which join to cluster
after their initialization. Test attached.

This message was sent by Atlassian JIRA

View raw message