[
https://issues.apache.org/jira/browse/KAFKA-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944402#comment-17944402
]
Jun Rao edited comment on KAFKA-19112 at 4/14/25 7:06 PM:
----------------------------------------------------------
[~chia7712] : For infinite retention, we already support that through the
following config. Relying on empty cleanup.policy seems redundant and
unintuitive.
h4. [https://kafka.apache.org/documentation/#brokerconfigs_log.retention.ms]
{code:java}
log.retention.ms
The number of milliseconds to keep a log file before deleting it (in
milliseconds), If not set, the value in log.retention.minutes is used. If set
to -1, no time limit is applied.
{code}
was (Author: junrao):
[~chia7712] : For infinite retention, we already support that through the
following config. Replying on empty cleanup.policy seems redundant and
unintuitive.
h4. [|https://kafka.apache.org/documentation/#brokerconfigs_log.retention.ms]
{code:java}
log.retention.ms
The number of milliseconds to keep a log file before deleting it (in
milliseconds), If not set, the value in log.retention.minutes is used. If set
to -1, no time limit is applied.
{code}
> cleanup.policy shouldn't be empty
> ---------------------------------
>
> Key: KAFKA-19112
> URL: https://issues.apache.org/jira/browse/KAFKA-19112
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jun Rao
> Assignee: 黃竣陽
> Priority: Major
> Labels: need-kip
>
> Currently, we allow a user to set cleanup.policy to be an empty list, which
> shouldn't be allowed. A few other configs of List type such as
> group.coordinator.rebalance.protocols and process.roles have the same
> problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
