Closed dharriso closed 1 day ago
Sorry the late answer. It will probably take some time before I can look at implementing a bean to call the key-value store. You are welcome to make a PR if it's urgent:)
no problems just wanted to know if it was on a roadmap.
I have now started implementing support for Key-Value store :) Hopefully I have a release ready next week
Brilliant, thats a great addition IMO. Look forward to see it go live
On Fri, May 31, 2024 at 11:04 AM Paw Figgé Kjeldgaard < @.***> wrote:
I have now started implementing support for Key-Value store :) Hopefully I have a release ready next week
— Reply to this email directly, view it on GitHub https://github.com/quarkiverse/quarkus-reactive-messaging-nats-jetstream/issues/86#issuecomment-2141686823, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGY6FOGLB2OJUO7V3YAS3TZFBDMTAVCNFSM6AAAAABGIWT2WSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBRGY4DMOBSGM . You are receiving this because you authored the thread.Message ID: <quarkiverse/quarkus-reactive-messaging-nats-jetstream/issues/86/2141686823 @github.com>
The latest release contains support for key / value store. I'm still missing to update documentation. But try look at the tests that see how to use it
Hi
Ive been looking at the suitability of the Quarkus NATS reactive messaging extension and noticed that the NATS Key-Value store API is not supported. Is this something you could consider adding?
NATS has a Key-Value store API that is used by the NATS community and would be a great addition for the Quarkus Reactive Message Extension for NATS.
See here, here & here
Thanks in advance Declan