[
https://issues.apache.org/jira/browse/KAFKA-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786575#comment-17786575
]
David Jameson commented on KAFKA-15821:
---------------------------------------
Had a go at this one because it looked like an easy fix and good first issue.
Let me know if I am missing anything. Thanks!
> Active topics for deleted connectors are not reset in standalone mode
> ---------------------------------------------------------------------
>
> Key: KAFKA-15821
> URL: https://issues.apache.org/jira/browse/KAFKA-15821
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.5.0, 2.6.0, 2.5.1, 2.7.0, 2.6.1, 2.8.0, 2.7.1, 2.6.2,
> 3.1.0, 2.6.3, 2.7.2, 2.8.1, 3.0.0, 3.0.1, 2.8.2, 3.2.0, 3.1.1, 3.3.0, 3.0.2,
> 3.1.2, 3.2.1, 3.4.0, 3.2.2, 3.2.3, 3.3.1, 3.3.2, 3.5.0, 3.4.1, 3.6.0, 3.5.1,
> 3.7.0
> Reporter: Chris Egerton
> Priority: Major
>
> In
> [KIP-558|https://cwiki.apache.org/confluence/display/KAFKA/KIP-558%3A+Track+the+set+of+actively+used+topics+by+connectors+in+Kafka+Connect],
> a new REST endpoint was added to report the set of active topics for a
> connector. The KIP specified that "Deleting a connector will reset this
> connector's set of active topics", and this logic was successfully
> implemented in distributed mode. However, in standalone mode, active topics
> for deleted connectors are not deleted, and if a connector is re-created, it
> will inherit the active topics of its predecessor(s) unless they were
> manually reset.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
