You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Anamika Nadkarni (Jira)" <ji...@apache.org> on 2021/08/31 06:42:00 UTC

[jira] [Created] (KAFKA-13255) Mirrormaker config property config.properties.exclude is not working as expected

Anamika Nadkarni created KAFKA-13255:
----------------------------------------

             Summary: Mirrormaker config property config.properties.exclude is not working as expected 
                 Key: KAFKA-13255
                 URL: https://issues.apache.org/jira/browse/KAFKA-13255
             Project: Kafka
          Issue Type: Bug
          Components: mirrormaker
    Affects Versions: 2.8.0
            Reporter: Anamika Nadkarni


Objective - Use MM2 (kafka connect in distributed cluster) for data migration between cluster hosted in private data center and aws msk cluster.

Steps performed -
 # Started kafka-connect service.
 # Created 3 MM2 connectors (i.e. source connector, checkpoint connector and heartbeat connector). Curl commands used to create connectors are in the attached file.  To exclude certain config properties while topic replication, we are using the 'config.properties.exclude' property in the MM2 source connector.

Expected -

Source topic 'dev.portlandDc.anamika.helloMsk' should be successfully created in destination cluster.

Actual -

Creation of the source topic 'dev.portlandDc.anamika.helloMsk' in destination cluster fails with an error. Error is
{code:java}
[2021-08-06 06:13:40,944] WARN [mm2-msc|worker] Could not create topic dev.portlandDc.anamika.helloMsk. (org.apache.kafka.connect.mirror.MirrorSourceConnector:371)
org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: confluent.value.schema.validation{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)