You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/12/04 18:22:00 UTC

[jira] [Resolved] (KAFKA-6150) Make Repartition Topics Transient

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

Guozhang Wang resolved KAFKA-6150.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0

Issue resolved by pull request 4270
[https://github.com/apache/kafka/pull/4270]

> Make Repartition Topics Transient
> ---------------------------------
>
>                 Key: KAFKA-6150
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6150
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>              Labels: operability
>             Fix For: 1.1.0
>
>
> Unlike changelog topics, the repartition topics could just be short-lived. Today users have different ways to configure them with short retention such as enforce a short retention period or use AppendTime for repartition topics. All these would be cumbersome and Streams should just do this for the users.
> One way to do it is use the “purgeData” admin API (KIP-107) such that after the offset of the input topics are committed, if the input topics are actually repartition topics, we would purge the data immediately.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)