oscerd commented on issue #1128: URL: https://github.com/apache/camel-kafka-connector/issues/1128#issuecomment-810323111
Now I noticed this line in your description "I was expecting the idempotency feature to re-consume the idempotency Kafka topic at offset 0 so it could have some kind of crash resilience." Basically the idempotency we are using is a camel concept. When you stop a consumer (camel consumer) with a kafka idempotent repository, the offset will be saved. When you restart the connector it will restart from that offset. This is mainly because the sftp component and the others works with just one consumer. In camel to support mutliple consumers we need to do some work on single component and it's not feasible on all the components, another possibility is to use some kind of lock mechanism with camel-master component. Sorry I didn't notice your sentence there. The behavior is normal from a Camel perspective. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
