StreamConfig adds discard_new_per_subject: boolean on servers 2.9.2 and better

[aricart]

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 discard policy is not new.

The new option will prevent a message from being added to a stream if the max_msgs_per_subject limit for the subject has been reached, returning a {"error":{"code":503,"err_code":10077,"description":"maximum messages per subject exceeded"}, "stream":"KV_A","seq":0}

Clients and Tools

• Schemas @ripienaar
• CLI @ripienaar
• Terraform @ripienaar support stream discard policies terraform-provider-jetstream#68
• Github Actions @ripienaar
• Go @piotrpio [ADDED] DiscardNewPerSubject to stream config nats.go#1102
• Java @scottf discard_new_per_subject nats.java#755
• JavaScript @aricart [FEAT] [JS] discard_new_per_subject functionality nats.deno#373
• .Net @scottf discard_new_per_subject nats.net#691
• C done by kozlovic [ADDED] JetStream: DiscardNewPerSubject stream configuration nats.c#593
• Python @wallyqs
• Ruby @wallyqs
• Rust @Jarema @caspervonb

Other Tasks

• docs.nats.io updated @jnmoyne
• Update ADR to Implemented
• Update client features spreadsheet

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.