You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today we have Nats-Expected-Last-Subject-Sequence that limits publishing to a stream if the previous message had a specific sequence
Along the same lines it would be useful to ensure only the first client can write a message when the subject is empty.
We discussed maybe (ab)using Nats-Expected-Last-Subject-Sequence:0 but decided not to, so maybe Nats-Expected-Empty-Subject:1
A sample use case could be for example registering a schema that relates to a specific topic, the first publisher to this topic should register the subject but that's true only ever once.
This setting should probably only be accepted in max_msgs_per_subject > 0 stream
The text was updated successfully, but these errors were encountered:
Feature Request
Use Case:
Today we have
Nats-Expected-Last-Subject-Sequence
that limits publishing to a stream if the previous message had a specific sequenceAlong the same lines it would be useful to ensure only the first client can write a message when the subject is empty.
We discussed maybe (ab)using
Nats-Expected-Last-Subject-Sequence:0
but decided not to, so maybeNats-Expected-Empty-Subject:1
A sample use case could be for example registering a schema that relates to a specific topic, the first publisher to this topic should register the subject but that's true only ever once.
This setting should probably only be accepted in
max_msgs_per_subject > 0
streamThe text was updated successfully, but these errors were encountered: