[
https://issues.apache.org/jira/browse/KAFKA-15478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Omnia Ibrahim updated KAFKA-15478:
----------------------------------
Labels: need-kip (was: )
> Update connect to use ForwardingAdmin
> -------------------------------------
>
> Key: KAFKA-15478
> URL: https://issues.apache.org/jira/browse/KAFKA-15478
> Project: Kafka
> Issue Type: New Feature
> Reporter: Omnia Ibrahim
> Priority: Major
> Labels: need-kip
>
> Connect uses AdminClients to create topics; while this simplifies the
> implementation of Connect it has the following problems
> * It assumes that whoever runs Connect 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 through admin client or using their centralised system or tools.
>
> We already have ForwardingAdmin in MM2 so we can extend connect to do
> something similiar
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
