You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Divij Vaidya (Jira)" <ji...@apache.org> on 2023/07/12 12:38:00 UTC

[jira] [Commented] (KAFKA-15132) Implement disable & re-enablement for Tiered Storage

    [ https://issues.apache.org/jira/browse/KAFKA-15132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742409#comment-17742409 ] 

Divij Vaidya commented on KAFKA-15132:
--------------------------------------

Update - need more time. new ETA 10th July.

> Implement disable & re-enablement for Tiered Storage
> ----------------------------------------------------
>
>                 Key: KAFKA-15132
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15132
>             Project: Kafka
>          Issue Type: New Feature
>          Components: core
>            Reporter: Divij Vaidya
>            Assignee: Divij Vaidya
>            Priority: Major
>              Labels: kip
>
> KIP-405 [1] introduces the Tiered Storage feature in Apache Kafka. One of the limitations mentioned in the KIP is inability to re-enable TS on a topic after it has been disabled.
> {quote}Once tier storage is enabled for a topic, it can not be disabled. We will add this feature in future versions. One possible workaround is to create a new topic and copy the data from the desired offset and delete the old topic. 
> {quote}
> This task will propose a new KIP which extends on KIP-405 to describe the behaviour on on disablement and re-enablement of tiering storage for a topic. The solution will apply for both Zk and KRaft variants.
> [1] KIP-405 - [https://cwiki.apache.org/confluence/display/KAFKA/KIP-405%3A+Kafka+Tiered+Storage] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)