[
https://issues.apache.org/jira/browse/IGNITE-10982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800435#comment-16800435
]
Roman Shtykh commented on IGNITE-10982:
---------------------------------------
[~Romeh] Let's work with continuous queries.
> Kafka Ignite connect module listen to all related cache node events, not only
> the source cache
> ----------------------------------------------------------------------------------------------
>
> Key: IGNITE-10982
> URL: https://issues.apache.org/jira/browse/IGNITE-10982
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 2.7
> Reporter: Mahmoud
> Priority: Major
>
> Hey All ,
> I see in Kafka module , in
> IgniteSourceTask.java , we listen to all target cache node events not only
> the source cache event , is it by design like that ? we should only listen to
> the source cache events through continuous query:
> [https://apacheignite.readme.io/docs/continuous-queries]
>
> As we current implementation , we catch all caches events the belong to the
> same source cache node , not only the configured source cache name:
> code snippet from : IgniteSourceTask.java
> {code:java}
> rmtLsnrId = IgniteGrid.getIgnite().events(IgniteGrid.getIgnite().cluster()
> .forCacheNodes(cacheName))
> .remoteListen(locLsnr, rmtLsnr, evts);{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
