You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Magesh kumar Nandakumar (JIRA)" <ji...@apache.org> on 2017/10/09 19:56:00 UTC

[jira] [Commented] (KAFKA-5295) Allow Kafka Connect source connectors to specify topic-specific settings for new topics

    [ https://issues.apache.org/jira/browse/KAFKA-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197606#comment-16197606 ] 

Magesh kumar Nandakumar commented on KAFKA-5295:
------------------------------------------------

[~rhauch] I  can pick this jira if its fine with you.

> Allow Kafka Connect source connectors to specify topic-specific settings for new topics
> ---------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5295
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5295
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.10.2.1
>            Reporter: Randall Hauch
>              Labels: needs-kip
>
> As of 0.11.0.0, Kafka Connect will be able to automatically create its internal topics using the new AdminClient (see KAFKA-4667). However, it still relies upon the broker auto-creating topics to which source connector records are written.
> Kafka Connect should use the AdminClient to explicitly create the new topics before writing the first source record to a new topic, and it should allow the connector the opportunity to customize the topic-specific settings for those new topics. As such, it will require a change in the public API (configs and/or framework) for source connectors and thus will require a KIP.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)