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 Tue, 28 Nov 2017 18:01:00 GMT

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

ASF GitHub Bot commented on KAFKA-6150:
---------------------------------------

GitHub user guozhangwang opened a pull request:

    https://github.com/apache/kafka/pull/4270

    [WIP] KAFKA-6150: Purge repartition topics

    *More detailed description of your change,
    if necessary. The PR title and PR message become
    the squashed commit message, so use a separate
    comment to ping reviewers.*
    
    *Summary of testing strategy (including rationale)
    for the feature or bug fix. Unit and/or integration
    tests are expected for any behaviour change and
    system tests should be considered for larger changes.*
    
    ### Committer Checklist (excluded from commit message)
    - [ ] Verify design and implementation 
    - [ ] Verify test coverage and CI build status
    - [ ] Verify documentation (including upgrade notes)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/guozhangwang/kafka K6150-purge-repartition-topics

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/4270.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #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
>
> 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)

Mime
View raw message