Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Status

Current state: Under DiscussionAccepted

Discussion thread: https://lists.apache.org/x/thread.html/rf65435729171c40a001a394e9f6170e7a2c24b6c9424a346954cd0e1@%3Cdev.kafka.apache.org%3E

JIRA:

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-10357

...

We propose to add two new exceptions MissingInternalTopicsException and MisconfiguredInternalTopicExceptionMissingInternalTopicsException is thrown when a required internal topic does not exist and MisconfiguredInternalTopicException is thrown when the internal topic is not configured as expected. In general, misconfigurations are configurations that differ from the default values specified by Kafka Streams or from configurations specified in user code where configurations in user code overwrite are considered before Streams' default values. Those misconfigurations typically occur if users change configurations directly on the brokers. For example, a changelog topic for a non-windowed state store is regarded as misconfigured if its retention period is not set to unlimited. Another example for a misconfigured internal topic is a repartition topic with the wrong number of partitions. In future, we might discover other misconfigurations that are critical to data loss. In such a case, Kafka Streams will also throw a MisconfiguredInternalTopicException without the need of a new KIP. The exception will contain a detailed explanation of what is wrong and how to fix it. The intended recipient of these exceptions is the operator, not software.

...