Hi Maxim,
I had a quick look, it seems like that was added to the Apache Kafka
documentation only in version 1.1.1, which didn't get a doc update being
only a patch version, so the relevant sentence is only in the docs for 2.0
[1].
Additionally, the passage was only added to the docs of the topic
https://www.cloudera.com/documentation/enterprise/properties/5-13-x/topics/cm_props_cdh5110_kafka.html
Mentions
log.retention.ms:
The maximum time before a new log segment is rolled out. If both
log.retention.ms and log.retention.bytes are set, a segment is deleted when
either limit is exceeded. T
Hi,
According to cloudera manager kafka documentation:
log.retention.ms: The maximum time before a new log segment is rolled out.
If both log.retention.ms and log.retention.bytes are set, a segment is
deleted when either limit is exceeded. The special value of -1 is
interpreted as unlimited. This p
There is difference between retention.bytes and retention.ms. Yes,
retention.bytes can be set to -1, but nowhere in the docs says about
retention.ms = -1
It might be possible that using -1 it's accepting as a "Value" - which
means it might not be validating. But it's not on official docs. I would
