[
https://issues.apache.org/jira/browse/KAFKA-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135220#comment-16135220
]
Dhananjay Patkar commented on KAFKA-5635:
-----------------------------------------
Thanks [~ewencp]
In my case, I am using kafka hosted as a cloud offering, I will check with them.
As per my understanding, my cloud provider is planning to expose a ReST
endpoint to publish and consume messages from Kafka. I thought its convenient
to capture data through ReST. But then I still need to incremental data push
and state management which kafka connect provides.
> 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
> 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
(v6.4.14#64029)
