[jira] [Resolved] (KAFKA-13401) Introduce a new Interface to manage Kafka resources in MM2

["Mickael Maison (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mickael Maison resolved KAFKA-13401.
------------------------------------
    Resolution: Fixed

> Introduce a new Interface to manage Kafka resources in MM2
> ----------------------------------------------------------
>
>                 Key: KAFKA-13401
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13401
>             Project: Kafka
>          Issue Type: Improvement
>          Components: mirrormaker
>            Reporter: Omnia Ibrahim
>            Assignee: Omnia Ibrahim
>            Priority: Major
>             Fix For: 3.4.0
>
>
> MM2 uses AdminClients to create and modify topics; while this simplifies the implementation of MM2 it has the following problems 
>  * It assumes that whoever runs MM2 must have admin access to both source and destination clusters. This assumption is not necessarily valid all the time.
>  * It creates conflict in use-cases where centralised systems or tools manage Kafka resources. 
> It would be easier if customers could provide how they want to manage Kafka topics and configs through admin client or using their centralised system or tools. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)