You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Randall Hauch (Jira)" <ji...@apache.org> on 2020/02/14 15:36:00 UTC

[jira] [Updated] (KAFKA-9556) KIP-558 cannot be fully disabled and when enabled topic reset not working on connector deletion

     [ https://issues.apache.org/jira/browse/KAFKA-9556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated KAFKA-9556:
---------------------------------
    Labels: topic-status  (was: )

> KIP-558 cannot be fully disabled and when enabled topic reset not working on connector deletion
> -----------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9556
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9556
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 2.5.0
>            Reporter: Randall Hauch
>            Assignee: Konstantine Karantasis
>            Priority: Blocker
>              Labels: topic-status
>             Fix For: 2.5.0
>
>
> According to KIP-558 for the new Connect topic tracking feature, Connect should not write the topic status records when the topic is disabled. However, currently that is not the case: when the new topic tracking (KIP-558) feature is disabled, Connect still writes topic status records to the internal status topic. 
> Also, according to the KIP, Connect should automatically reset the topic status when a connector is deleted, but that is not happening.
> It'd be good to increase test coverage on the new feature.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)