[
https://issues.apache.org/jira/browse/KAFKA-14021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860185#comment-17860185
]
Chris Egerton commented on KAFKA-14021:
---------------------------------------
No, the consumer does not rely on committed offsets for subsequent polls. It
automatically tracks the offsets it will fetch from based on the offsets for
prior fetches.
> MirrorMaker 2 should implement KIP-618 APIs
> -------------------------------------------
>
> Key: KAFKA-14021
> URL: https://issues.apache.org/jira/browse/KAFKA-14021
> Project: Kafka
> Issue Type: Improvement
> Components: connect, mirrormaker
> Reporter: Chris Egerton
> Assignee: Chris Egerton
> Priority: Major
> Fix For: 3.5.0
>
>
> The {{MirrorSourceConnector}} class should implement the new APIs added by
> KIP-618.
> This includes the
> [SourceConnector::exactlyOnceSupport|https://github.com/apache/kafka/blob/025e47b8334eb7125c7fdd2f725a2fef3c98344c/connect/api/src/main/java/org/apache/kafka/connect/source/SourceConnector.java#L34-L54]
> method and, potentially, the
> [SourceConnector::canDefineTransactionBoundaries|https://github.com/apache/kafka/blob/025e47b8334eb7125c7fdd2f725a2fef3c98344c/connect/api/src/main/java/org/apache/kafka/connect/source/SourceConnector.java#L56-L73]
> method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
