Source topic offsets
Source topic offsets are stored in two different consumer groups. The first is the sink-managed consumer group defined by the iceberg.control.group-id property. The second is the Kafka Connect managed consumer group which is named connect- by default. The sink-managed consumer group is used by the sink to achieve exactly-once processing. The Kafka Connect consumer group is only used as a fallback if the sink-managed consumer group is missing. To reset the offsets, both consumer groups need to be reset.
But, I hope the README contents will be more detailed.
Related questions)
Does reset order matter between sink-managed consumer group offset and Kafka Connect managed consumer group offset? Each order is better to apply reset? (The order don't matter, if the sink connector is STOPPED? )
Then, is total procedure of resetting consuming offset like below?
stop sink connector
reset sink-managed consumer group & Kafka Connect managed consumer group
On README, there is a section related to this.
Source topic offsets Source topic offsets are stored in two different consumer groups. The first is the sink-managed consumer group defined by the iceberg.control.group-id property. The second is the Kafka Connect managed consumer group which is named connect- by default. The sink-managed consumer group is used by the sink to achieve exactly-once processing. The Kafka Connect consumer group is only used as a fallback if the sink-managed consumer group is missing. To reset the offsets, both consumer groups need to be reset.
But, I hope the README contents will be more detailed.
Related questions)
Does reset order matter between
sink-managed consumer group
offset andKafka Connect managed consumer group
offset? Each order is better to apply reset? (The order don't matter, if the sink connector is STOPPED? )Then, is
total procedure of resetting consuming offset
like below?sink-managed consumer group
&Kafka Connect managed consumer group