oscerd commented on issue #1682: URL: https://github.com/apache/camel-kafka-connector/issues/1682#issuecomment-6632223120
The duplicates after a restart are expected with `camel.idempotency.repository.type=memory`, because the in-memory repository starts empty every time the task starts. If the objects must stay in S3, the aws-s3-source Kamelet can move them to another bucket instead of deleting them (`camel.kamelet.aws-s3-source.moveAfterRead=true` with `camel.kamelet.aws-s3-source.destinationBucket`), or you can keep them and use the Kafka idempotent repository, which survives restarts. That repository is currently created from `camel.idempotency.kafka.bootstrap.servers` alone, with no way to pass SSL/SASL settings, so it cannot reach a secured cluster like yours; that limitation is tracked in #1497, so closing this as a duplicate of it. Separately, on 4.22.0 the aws-s3-source connector can re-read the same objects for another reason, which is tracked in #1849. --- _Claude Code on behalf of Andrea Cosentino_ -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
