Hello, You can use QueryCursor and calling .close() method for stop ContinuousQuery[1]. Also you can store cursor in order to close it in future.
If you want use service, wich starts ContinuousQuery. You can deploy singleton service[2] with specific name and cancel the service if it necessary. CnonContinuousQuery must be stopped in cancel method of the service implementation. [1]: https://apacheignite.readme.io/docs/continuous-queries [2]: https://apacheignite.readme.io/docs/service-example On Thu, Jun 23, 2016 at 1:00 AM, ChickyDutt <[email protected]> wrote: > Hi Team > > > Attached is the diagram depicting my use-case. > > I want you to help me understand in what form should I deploy the > Continuous query if I want the freedom to srat and stop it on the fly. > > Can I deploy it as a service? Will it then be possible for me to start and > stop a deployed service if I were to encounter an exception? > > Could you please advise in what other forms could I implement a continuous > query with the freedom to stop it when encountering exceptions. > > In addition to the above, how do I stop a continuous query? > > Please let me know if you need any further information. > > Regards, > Ashish Sharma. > > *TransactionPipeline.docx* (53K) Download Attachment > <http://apache-ignite-users.70518.x6.nabble.com/attachment/5810/0/TransactionPipeline.docx> > > ------------------------------ > View this message in context: Transaction Pipeline. > <http://apache-ignite-users.70518.x6.nabble.com/Transaction-Pipeline-tp5810.html> > Sent from the Apache Ignite Users mailing list archive > <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. > -- Vladislav Pyatkov
