Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Update Topic configuration from topic.properties on topic provisioning
See original GitHub issueIt seems that topic configuration done via spring.cloud.stream.kafka.bindings.<binding>.consumer.topic.properties and
spring.cloud.stream.kafka.bindings.<binding>.producer.topic.properties do not update the topic configuration if the topic already exsists.
It is possible to update a topic configuration via kafka-admin-client like this.
In my opinion it would be a nice feature to modify the topic configuration to fully manage topics from the application.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As a work around, you can disable the code by setting
autoCreateTopicstofalse(after the app has run the first time).It probably should have gotten its own property
autoAlterTopics(default false).I believe that’s a bug; please open a new issue - we don’t (as far as I know) require a minimum broker level, and certainly we shouldn’t impose that in a point release SR8->SR9. I think a
try/catchshould be added.