Proposed change
When working with jetstream, usually, we place stream configs in application resource directory.
We can upsert a stream with
StreamConfiguration.instance(jet.toJson())
, where jet is Json representation of corresponding stream config. This approach It is very easy and straightforward.
We've tried KV to see if we can replace Redis, but KV Configuration doesn't have similar builder and primary constructor is package private.
Use case
Storing stream config in application resource directory. Since configuration can be saved as Json, reverse mechanism would be nice.
Contribution
The change is very trivial, primary question if this proposal is acceptable at all.
Proposed change
When working with jetstream, usually, we place stream configs in application resource directory.
We can upsert a stream with
, where jet is Json representation of corresponding stream config. This approach It is very easy and straightforward.
We've tried KV to see if we can replace Redis, but KV Configuration doesn't have similar builder and primary constructor is package private.
Use case
Storing stream config in application resource directory. Since configuration can be saved as Json, reverse mechanism would be nice.
Contribution
The change is very trivial, primary question if this proposal is acceptable at all.