Fix docs for missingTopicsFatal: false by default

This commit is contained in:
Gary Russell
2019-12-11 09:19:44 -05:00
parent 45902a5770
commit e12c2856f4

View File

@@ -747,7 +747,7 @@ By default, logging of topic offset commits is performed at the `DEBUG` logging
Starting with version 2.1.2, a property in `ContainerProperties` called `commitLogLevel` lets you specify the log level for these messages.
For example, to change the log level to `INFO`, you can use `containerProperties.setCommitLogLevel(LogIfLevelEnabled.Level.INFO);`.
Starting with version 2.2, a new container property called `missingTopicsFatal` has been added (default: `true`).
Starting with version 2.2, a new container property called `missingTopicsFatal` has been added (default: `false` since 2.3.4).
This prevents the container from starting if any of the configured topics are not present on the broker.
It does not apply if the container is configured to listen to a topic pattern (regex).
Previously, the container threads looped within the `consumer.poll()` method waiting for the topic to appear while logging many messages.