Re: KafkaSinglePortExactlyOnceOutputOperator throwing exception about violation about Exactly once

Thanks Sandesh.. It helped Regards Vivek -- Sent from: http://apache-apex-users-list.78494.x6.nabble.com/

Re: KafkaSinglePortExactlyOnceOutputOperator throwing exception about violation about Exactly once

1. Upstream needs to be idempotent, if not then during recovery you will see that exception. 2. If you are using a custom tuple, please make sure that it HashCode & Equals methods are properly implemented. On Wed, Mar 14, 2018 at 10:09 AM Vivek Bhide wrote: > Exception

Re: KafkaSinglePortExactlyOnceOutputOperator throwing exception about violation about Exactly once

Exception stack trace is below 2018-03-13 17:00:53,219 INFO com.datatorrent.stram.StreamingContainerManager: Container container_1520983362676_0002_01_07 buffer server: 80e65028f6a8:60970 2018-03-13 17:00:54,811 INFO com.datatorrent.stram.StreamingContainerParent: child msg: Stopped running

Re: KafkaSinglePortExactlyOnceOutputOperator

Yes, it may be better to pull out the topic selection into an upstream operator that emits the messages on separate ports per topic and then you can use the exactly-once output operator without customization. On Wed, Oct 12, 2016 at 11:29 AM, Bandaru, Srinivas < srinivas.band...@optum.com>

RE: KafkaSinglePortExactlyOnceOutputOperator

Just a correction for use case. Use case: kafka producer emits messages and processing messages using Datatorrent application, Based on the DT application logic divide the messages into two different groups and write it to two different kafka topics Thanks, Srinivas From: Bandaru, Srinivas