[
https://issues.apache.org/jira/browse/KAFKA-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-10333.
------------------------------------
Fix Version/s: 2.8.0
Resolution: Duplicate
DUP of KAFKA-10833
> Provide an API to retrieve Kafka Connect task configurations
> ------------------------------------------------------------
>
> Key: KAFKA-10333
> URL: https://issues.apache.org/jira/browse/KAFKA-10333
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Mickael Maison
> Assignee: Mickael Maison
> Priority: Major
> Fix For: 2.8.0
>
>
> Kafka Connect exposes an API to retrieve configurations from connectors.
> Connectors are responsible for creating tasks. When doing so, they have to
> build configurations for individual tasks. In some case, the configuration
> can be passed as is to tasks but in some others, the configuration is mutated
> to make tasks do specific work.
> For example with MirrorSourceConnector, the connector configuration has a
> field "topics" which is a list of topics and patterns to mirror. When the
> connector builds task configurations, it resolves the list of topic names and
> patterns to exact partitions and spread the partitions over all the tasks.
> It would be useful to identify the exact configuration each task is given.
> For MM2, it would allow identifying the partitions that matched the topics
> field. I would also help understanding the impact when a task fails
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
