m] On Behalf Of Nikolay
Izhikov
Sent: Monday, May 7, 2018 6:40 PM
To: user@ignite.apache.org
Cc: JP
Subject: Re: Continuous query - Exactly once based event across multiple
nodes..
Hello, JP.
You should use target node in remote filter.
You should check "Is primary node for some record equal
JP,
Do you have a solution for this? Do you need any more help?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Vkulichenko,
I want to update in multiple databases based on event triggered in the
ignite cache.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
JP,
Can you please describe the business case behind this? What are you trying
to achieve on application level? What guarantees are needed and why?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello, JP.
So what?
What is issue with multiple filter instance?
пн, 7 мая 2018 г., 12:47 JP :
> Thanks... This solution worked but problem is, it creating multiple remote
> filter instance..
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Thanks... This solution worked but problem is, it creating multiple remote
filter instance..
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello, JP.
You should use target node in remote filter.
You should check "Is primary node for some record equal to target node?" in
your filter.
Please, see code below.
You can find related discussion and full example here [1].
@IgniteAsyncCallback
public static class RemoteFactory impl
