oscerd commented on issue #1561: URL: https://github.com/apache/camel-kafka-connector/issues/1561#issuecomment-6632180877
Closing this as answered, since a partition- and offset-preserving backup is not something the MinIO connectors can do. Offsets cannot be restored by any producer, because Kafka assigns them on write; the source connector always leaves the partition to Kafka's partitioner, and the minio-sink Kamelet stores only the record value (the key is available to the route as the `camel.kafka.connector.record.key` header but is not written to the object). If the original partitions came from the key and the new topic has the same partition count, restoring the keys (with a custom route or SMT, plus `camel.source.camelMessageHeaderKey` on the source side) puts records back on the same partitions; for an exact copy, a dedicated Kafka backup or replication tool is a better fit. If you would like connector support for part of this, such as exposing the record partition as a header, please open a new feature request against 4.22.x. --- _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]
