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

["Randall Hauch (JIRA)" <ji...@apache.org>]

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

Randall Hauch commented on KAFKA-5295:
--------------------------------------

Created [KIP-158|https://cwiki.apache.org/confluence/display/KAFKA/KIP-158%3A+Kafka+Connect+should+allow+source+connectors+to+set+topic-specific+settings+for+new+topics] to discuss how to change the public API for Connect to make this possible. Discussions welcome on the [mailing list thread|https://www.mail-archive.com/dev@kafka.apache.org/msg73775.html] mentioned at the top of the KIP.

> 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
>            Assignee: 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.3.15#6346)