Scott Fauerbach
Scott Fauerbach
## Overview Should a bind subscription be required to validate against subscribe subject / filter and other subscribe option logic like preventing consumer configuration changes, or should a bind ignore...
## Overview Should subscription api allow null/empty/undefined subject when both stream and durable [consumer] name are supplied? Only in case of bind? This would also require that the durable exists,...
## Overview See [ADR 8 KV Status interface changes](https://github.com/nats-io/nats-architecture-and-design/pull/159) Status now exposes: ``` // Bytes returns the size in bytes of the bucket Bytes() uint64 ``` ## Clients and Tools...
## Overview Based on conversation, the expectation is choice #4 Reject any attempt to create a subscription against an existing durable unless the subscription is a bind subscription or the...
## Overview Support for MaxBytes for pull requests including changes to Consumer Configuration and JSApiConsumerGetNextRequest See [Server PR 3126](https://github.com/nats-io/nats-server/pull/3126) The Consumer Configuration now includes `max_expires` and `max_bytes` ``` MaxRequestExpires time.Duration...
## Overview In August '21, `consumer_info.delivered` and `consumer_info.ack_floor` were changed from `sequence_pair` to `sequence_info` The difference in these objects is that the `sequence_info` has `last_active` where the `sequence_pair` does not....
## Overview It is valid to have the uri encoded. ``` tls://user:Rmwuukd0QsJI%5ERMkFGHz1J7vjz0A%2A27oCA%23j6%21WYf%23@host:4222 ``` where the password is actually ``` Rmwuukd0QsJI^RMkFGHz1J7vjz0A*27oCA#j6!WYf# ``` ## Clients and Tools - [x] Schemas @ripienaar -...
## Overview On subscriptions made for pull consumers when the user has asked to "bind", there are conditions when the consumer info lookup will fail, namely when the consumer is...
## Overview Add an option to instruct client to ignore discovered URLs from server INFO messages, and use only the initial Connect URL. The [Issue 891](https://github.com/nats-io/nats.go/issues/891) from nats.go repo has...
## Overview For the message delete request `STREAM.MSG.DELETE.%s` the payload json has been expanded to contain a no_erase field. * The false/default setting overwrites the message deleted by the api...