Open suikast42 opened 3 months ago
Watch uses ordered consumer, which might be recreated on the fly if it discovers any issue.
Because of that, it needs random name.
However, we can consider adding possibility to fill the watcher's Consumer Metadata
with information allowing you to identify it in other way than by checking on which stream it is, or which KV it is watching.
Would that address your case?
The stream name is already included.
Proposed change
I am using the jnats java libraray an subsribe to a kv bucket with
This generates on every boot different consumer name
Is it possible to add consumer name to KeyValueWatchOption ?
Use case
Listen to KV stores
Contribution
No response