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
Ephemeral consumers can supply inactive_threshold. The server defaults if not supplied.
Durable consumers still must supply durable_name.
name is not required if durable_name is supplied.
If a user supplies both name and durable_name they must be the same, otherwise the server will respond with an error 10017 "consumer name in subject does not match durable name in request". Client side validation of this should be consistent with other behavior in your client.
If the server is v2.9.0 or later and the user does not provide a name or durable_name, just use the original ephemeral template $JS.API.CONSUMER.CREATE.<stream_name>
If the server is older than v2.9.0 and the user provides a name, the client should return/throw an error since the old templates/server does not support ephemeral name and the server will supply one that will not match what the client set.
The changes is for JS API security enablement and makes it possible to grant permissions to an account/user to create consumers on a stream having a specific filter.
Prefixes
All prefix rules apply as always regarding the $JS.API. portion of the template.
Client authors please update with your progress. If you open issues in your own repositories as a result of this request, please link them to this one by pasting the issue URL in a comment or main issue description.
The text was updated successfully, but these errors were encountered:
Overview
Reference PR nats-io/nats-server#3409 for changes to consumer creation.
Consumer Configuration
name
.inactive_threshold
. The server defaults if not supplied.durable_name
.name
is not required ifdurable_name
is supplied.name
anddurable_name
they must be the same, otherwise the server will respond with an error 10017 "consumer name in subject does not match durable name in request". Client side validation of this should be consistent with other behavior in your client.name
ordurable_name
, just use the original ephemeral template$JS.API.CONSUMER.CREATE.<stream_name>
name
, the client should return/throw an error since the old templates/server does not support ephemeral name and the server will supply one that will not match what the client set.JS.API Templates v2.9.0
The new base template for creating consumers:
consumerName
would be thename
for ephemerals,durable_name
for durables.Filter Subjects
If the user specifies a filter subject other than
>
, this should be specified as the last segment.so for example
The changes is for JS API security enablement and makes it possible to grant permissions to an account/user to create consumers on a stream having a specific filter.
Prefixes
All prefix rules apply as always regarding the
$JS.API.
portion of the template.Clients and Tools
Name
in consumer configuration nats.c#580Other Tasks
Implemented
Client authors please update with your progress. If you open issues in your own repositories as a result of this request, please link them to this one by pasting the issue URL in a comment or main issue description.
The text was updated successfully, but these errors were encountered: