kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias J. Sax (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-7930) StreamsResetter makes "changelog" topic naming assumptions
Date Thu, 21 Feb 2019 07:45:00 GMT

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

Matthias J. Sax resolved KAFKA-7930.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

> StreamsResetter makes "changelog" topic naming assumptions
> ----------------------------------------------------------
>
>                 Key: KAFKA-7930
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7930
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams, tools
>    Affects Versions: 2.1.0
>            Reporter: Murad M
>            Priority: Major
>              Labels: features, needs-kip, patch-available, usability
>             Fix For: 2.3.0
>
>
> StreamsResetter deletes the topics considered internal. Currently it just checks the
naming as per [code|https://github.com/apache/kafka/blob/1aae604861068bb7337d4972c9dcc0c0a99c374d/core/src/main/scala/kafka/tools/StreamsResetter.java#L660].
If assumption is wrong (either topic prefix or suffix), tool becomes useless if aware even
dangerous if not. Probably better either:
>  * naming assumption should be optional and supply internal topics with argument (--internal-topics)
>  * deletion could be optional (--no-delete-internal)
>  * ignore topics which are included in list of --input-topics
> Faced this, when was trying to reset applications with GlobalKTable topics named as *-changelog.
Such topics sometimes are not desirable for deletion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message