[
https://issues.apache.org/jira/browse/KAFKA-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227688#comment-16227688
]
Guozhang Wang commented on KAFKA-6150:
--------------------------------------
This is my proposed steps to tackle this JIRA with smaller PRs:
1. Add the AdminClient module into KafkaStreams' ClientSupplier (note we will
need this client anyways to eventually replace the StreamsKafkaClient).
2. At the same time, help reviewing and merging in KAFKA-5925 (KIP-204) to add
the deleteRecords API in the AdminClient.
3. Use the AdminClient's newly added API to issue deleteRecord requests at
commit intervals in the async manner.
cc [~mjsax]
> 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)
