[
https://issues.apache.org/jira/browse/KAFKA-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantine Karantasis resolved KAFKA-5635.
-------------------------------------------
Resolution: Won't Fix
> KIP-181 Kafka-Connect integrate with kafka ReST Proxy
> -----------------------------------------------------
>
> Key: KAFKA-5635
> URL: https://issues.apache.org/jira/browse/KAFKA-5635
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Dhananjay Patkar
> Priority: Major
> Labels: features, newbie
>
> Kafka connect currently uses kafka clients which directly connect to kafka
> brokers.
> In a use case, wherein I have many kafka connect [producers] running remotely
> its a challenge to configure broker information on every connect agent.
> Also, in case of IP change [upgrade or cluster re-creation], we need to
> update every remote connect configuration.
> If kafka connect source connectors talk to ReST endpoint then client is
> unaware of broker details. This way we can transparently upgrade / re-create
> kafka cluster as long as ReST endpoint remains same.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
