Alberto Ricart

AckNext

1

## AckNext functionality The server API has always supported the ability to `ack` and `next` using a single response. This functionality seems to work correctly on the server, and we...

Discussion: Consumer and Stream Name Validation

7

## Overview Initial validation for streams and consumer names included `.`, `*`, or `>` in the names. The ADR for the KV specified bucket names to be `^[a-zA-Z0-9_-]+$`. This regex...

List materialized views

5

## Overview Go client started listing materialized views like KVs directly. This is useful as it allows the user to list all KVs or ObjectStores returning a value that aligns...

## Overview See [ADR-17 Order Consumer changes](https://github.com/nats-io/nats-architecture-and-design/pull/161) ### Consumer Configuration setting changes: - mem_storage: must not be provided or set to true. Set to true if it is not provided....

## Overview Stream configuration now adds the boolean property `discard_new_per_subject`. This new option works in conjunction of the `discard` and it is not valid (rejected by the server) if the...

## Overview Stream list (`STREAM.LIST`) can now specify an optional payload `{subject: "a.subject.>"}` to filter the list of streams returned to those capturing the specified subject filter. if your client...

## Overview Pull consumers now support `all` (AckAll) and `none` (AckNone) policies. If your client placed any restrictions such policies, they should be removed. ## Clients and Tools - [x]...

## Overview Stream info requests can now result in paginated responses. The pagination is will trigger if the request includes a `subjects_filter`, which would include more than 100,000 subject entries...

ConsumerConfig `filter_subject` can now be updated by a client

3

## Overview Previously, the server would reject changes to `filter_subject` - the following PR removes this limitation: https://github.com/nats-io/nats-server/pull/3216 ## Clients and Tools - [x] Schemas @ripienaar - [x] CLI @ripienaar...