Tim Van Laer created KAFKA-7803:
-----------------------------------
Summary: Streams internal topics config is not updated when the
code is changed
Key: KAFKA-7803
URL: https://issues.apache.org/jira/browse/KAFKA-7803
Project: Kafka
Issue Type: Improvement
Components: streams
Reporter: Tim Van Laer
Considering the following state store definition:
{code:java}
ImmutableMap<String, String> changelogTopicConfig = new
ImmutableMap.Builder<String, String>()
.put(TopicConfig.SEGMENT_BYTES_CONFIG, String.valueOf(100 * 1024 * 1024))
.build();
builder.addStateStore(
Stores.keyValueStoreBuilder(Stores.persistentKeyValueStore("store-example"),
Serdes.String(), Serdes.String())
.withLoggingEnabled(changelogTopicConfig)
);{code}
The configuration for a changelog topic (segment size, max message size...) is
used when Kafka Streams create the internal topic (See
[InternalTopicManager|https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/processor/internals/InternalTopicManager.java]).
If I later decide to increase the segment size, I would update the value in
the code. However Kafka Streams currently won't apply this code change to the
internal topic config. This causes a confusing state where the code is
different from the actual runtime.
It would be convenient if Kafka Streams could reflect those changes to the
internal topic by updating the topic configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
