[
https://issues.apache.org/jira/browse/KAFKA-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135815#comment-17135815
]
Ryanne Dolan commented on KAFKA-10160:
--------------------------------------
Agree this is a bug. This property is hard-coded but doesn't need to be. MM2
should probably default to earliest, but shouldn't override the property if
it's manually configured, IMO.
> Kafka MM2 consumer configuration
> --------------------------------
>
> Key: KAFKA-10160
> URL: https://issues.apache.org/jira/browse/KAFKA-10160
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.5.0, 2.4.1
> Reporter: Pavol Ipoth
> Priority: Major
> Labels: configuration, kafka, mirror-maker
>
> [https://github.com/apache/kafka/blob/trunk/connect/mirror/src/main/java/org/apache/kafka/connect/mirror/MirrorMakerConfig.java#L51,]
> according this producer/consumer level properties should be configured as
> e.g. somesource->sometarget.consumer.client.id, i try to set
> somesource->sometarget.consumer.auto.offset.reset=latest, but without
> success, consumer always tries to fetch earliest, not sure if bug or my
> misconfiguration, but then at least some update to docu would be useful
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
