Guozhang Wang commented on KAFKA-6535:

I think it may be brining more operational risk than benefit in practice: 
knowing that some topics is not used by any other teams for sure is hard, so 
opening this door to allow users to this, mistakenly, may lead to more issues.

Instead, we should just encourage users to use internal topics when possible 
unless there are reasons not to, so far we have the following reasons that I 
think we can fix in the near future, so it would be still a good approach for 
encouraging internal topics moving forward:

1. Users want to override {{num.partitions}} and other configs for separate 
topics; this is being discussed in some KIPs already.
2. Users want to maintain the topic names for extensibility (upgrading the app 
without restarting a new app, for example); this is also being discussed to be 
better supported in the future.

> Set default retention ms for Streams repartition topics to infinity
> -------------------------------------------------------------------
>                 Key: KAFKA-6535
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6535
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Guozhang Wang
>            Priority: Major
>              Labels: needs-kip, newbie
> After KIP-220 / KIP-204, repartition topics in Streams are transient, so it 
> is better to set its default retention to infinity to allow any records be 
> pushed to it with old timestamps (think: bootstrapping, re-processing) and 
> just rely on the purging API to keeping its storage small.

This message was sent by Atlassian JIRA

Reply via email to