kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6150) Make Repartition Topics Transient
Date Mon, 04 Dec 2017 18:24:00 GMT

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

ASF GitHub Bot commented on KAFKA-6150:

Github user asfgit closed the pull request at:


> 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

View raw message