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.
Improve support for Kafka Streams interactive queries
See original GitHub issueDescription
The idea would be to industrialize the support of Kafka Streams interactive queries when “querying remote state stores for the entire app”.
This was discussed in https://github.com/quarkusio/quarkus-quickstarts/pull/578 , as the quickstart demonstrates interactive queries, but it’s not very test-friendly and requires some boilerplate config.
Implementation ideas
It looks like the extension could pre-configure quarkus.kafka-streams.application-server to ${hostname}:${quarkus.http.port}, if a quarkus http extension (“RPC endpoint”) is also present.
Relying on the presence of a HOSTNAME env variable is not cross-platform, so it might be necessary to determine it programmatically via Java INetAddress APIs (similar to https://github.com/quarkusio/quarkus/blob/e50393a3cb37a2a444210160fc88c953e81da55d/core/runtime/src/main/java/io/quarkus/runtime/logging/LoggingSetupRecorder.java#L328 )
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (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
@ejba The problem is that the default value needs to be resolved programmatically, which happens after any mandatory/optional config is validated.
Can this issue be closed?