[
https://issues.apache.org/jira/browse/KAFKA-9556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037337#comment-17037337
]
ASF GitHub Bot commented on KAFKA-9556:
---------------------------------------
hachikuji commented on pull request #8085: KAFKA-9556: Fix two issues with
KIP-558 and expand testing coverage
URL: https://github.com/apache/kafka/pull/8085
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
