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.
PartitionKeyExtractorStrategy instances do not have access to application context
See original GitHub issueWhen selecting the partion of a kafka topic using a custom PartitionKeyExtractorStrategy, the instantiated objects are not initialized to use configuration values or beans from the application context. This would be very useful when selecting the partition based on a configurable value.
I have a provided a demo. When starting it, the logging shows that the inserted @Value is null and not properly initialized.
If this is on purpose the documentation should provide more information what is initialized into the this object.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 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
Maybe replace it with a
beanName?This was a carry-over from Spring XD where it was less-easy to add custom beans to the context.
@garyrussell @ilayaperumalg I am reviewing https://github.com/spring-cloud/spring-cloud-stream/issues/760 - wondering if we should consider deprecating this mechanism in a future release (1.2?) - at the risk of disabling creating such configurations per-binding. The whole mechanism is somewhat un-Spring-like.