Hi David, I would implement this using custom events in the following way:
- introduce your custom event - TransactionEvent and send it every time to subscribers a transaction succeeds using IgniteEvents.recordLocal(…) method. The event can contain any info you need. - the separate process can subscribe for your custom TransactionEvents, process them and publish to Kafka. This will let you to decouple Ignite logic from Kafka logic. Below is a code snippet that demonstrates how to use custom events in general: https://gist.github.com/dmagda/f1b93a9aa4774a360465bc9f63cc58c9 Will this work for you? — Denis > On Jun 1, 2016, at 9:09 PM, David Robinson <[email protected]> wrote: > > I can - but apparently not with a separate process that gets notifications - > which is the design point I was seeking. > Thanks again. > > On Wed, Jun 1, 2016 at 12:55 PM, Alexei Scherbakov > <[email protected] <mailto:[email protected]>> wrote: > You can easily implement such a thing as a part of transaction logic. > > > 2016-06-01 14:52 GMT+03:00 limabean <[email protected] > <mailto:[email protected]>>: > Hi Alexi, > > Thank you for the clarification. > > My final goal is to notify other processes not related to the grid > application about changes to the data caches. For example, it would be nice > to have a Kafka publisher registered as a transaction listener and then when > it gets transaction events, publish this information to a Kafka topic. > > Ignite is good at pulling data in, but it needs to be equally good at > sharing data to work well in my environment. > > What do you think ? > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/listening-for-events-on-transactions-tp5346p5357.html > > <http://apache-ignite-users.70518.x6.nabble.com/listening-for-events-on-transactions-tp5346p5357.html> > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > > > > -- > > Best regards, > Alexei Scherbakov >
