2.15.7 Support Server v2.9.0 and Object Store Experimental

IMPORTANT

This release uses a new consumer create API when interacting with nats-server version 2.9.0 or higher. This changes the subjects used by the client to create consumers, which might in some cases require changes in access and import/export configuration.

JetStream / Management

• Get Message Enhancement #696 @scottf
• No Erase option on message delete #698 @scottf
• Support v2.9.0 Get Direct Message feature #701 #703 @scottf
• Support v2.9.0 Consumer Create feature #723 #725 @scottf

Key Value

• Fix bug to return null instead of entry on get of deleted or purged key #700 @scottf
• Allow direct configuration for KV #718 #724 @scottf

Object Store

• Initial implementation, experimental. #705 #714 #720 @scottf

Core

• Static Memory Auth Handler #702 @scottf
• Support v2.9.0 stream configuration republish #709 @scottf

2.15.6 new Consumer configuration fields

Core

• better request timeout management #693 @scottf

JetStream

• support num_replicas and mem_storage in consumer configuration #689 @goku321 @scottf

Misc

• Change example to have more flexibility on message size #690 @scottf

2.15.5 re-release 2.15.4

Core

• Accept encoded connection urls #674 @scottf
• Only track duplicate responses when advanced tracking is on #659 @scottf

JetStream

• revert ConsumerConfiguration changes where some fields were downgraded #685 @scottf
• consumer info change to sequence_info from sequence_pair #679 @scottf
• consumer filter subject is now modifiable #676 @scottf
• handle updated account stats #668 @scottf
• Ability to create an External object #661 @scottf

KV

• ability to update bucket config #662 @scottf

Experimental

• expose management getStreamNamesBySubjectFilter #681 @scottf
• experimental pull reader #683 @scottf

Tests

• Add test for NKey.clear #663 @lacinoire

Misc

• remove comments that say durable is required during pull #675 @scottf
• better push queue example #670 @scottf
• fix inactive threshold doc #660 @scottf

2.15.4 fixes, enhancements and experimental

Core

• Accept encoded connection urls #674 @scottf
• Only track duplicate responses when advanced tracking is on #659 @scottf

JetStream

• consumer info change to sequence_info from sequence_pair #679 @scottf
• consumer filter subject is now modifiable #676 @scottf
• handle updated account stats #668 @scottf
• Ability to create an External object #661 @scottf

KV

• ability to update bucket config #662 @scottf

Experimental

• expose management getStreamNamesBySubjectFilter #681 @scottf
• experimental pull reader #683 @scottf

Tests

• Add test for NKey.clear #663 @lacinoire

Misc

• remove comments that say durable is required during pull #675 @scottf
• better push queue example #670 @scottf
• fix inactive threshold doc #660 @scottf

2.15.3 Writeable Placement

JetStream

• Ability for user to create a Placement object PR #655 @scottf

2.15.2 JetStream Improvements

JetStream

• Pull config changes, ephemeral pull, unit tests PR #645 @scottf
• Server urls connection management PR #648 @scottf
  • Architecture issue 113 Add option to ignore discovered urls
  • ServersToTryProvider provide a way that a user can provide a complete custom implementation to provide the server urls to try on connect / reconnect. Tiered servers could be implemented this way. EXPERIMENTAL feature.
• EXPERIMENTAL PullRequestOptions PR #649 @scottf

2.15.1 Remove batch size limitations and add 409 support

JetStream

• Remove pull batch size limitation PR #642 @scottf
• Statuses with code 409 are known statuses PR #643 @scottf

2.15.0 Subscription must be made before consumer is created

The order of creating a subscription on the server and creating a consumer on the server matters. Once the consumer is created, there is interest and the server tries to deliver. But if the subscription is not created, the messages are delivered to...nowhere, but are considered delivered.

This was not strictly a problem but it was a race - if the subscription was ready before the consumer was sent messages, then things went fine. Unit test didn't fail. But when we were testing against NGS and in clusters with mixes of JetStream and non-Jetstream servers, the consumer was always ready because of simple latency.

So now the server subscription is always made first avoiding the problem altogether.

See PR #639

2.14.2 Consumer Configuration Change Validation

Improvements

PR #637

• Added additional validation (unit testing) in relation to PR #635 Improve subscription creation with existing durable to be smarter when comparing provided configuration with server configuration.
• Added more information to the exception message text by including a list of fields that caused the issue.

2.14.1 Improvements, client parity, docs, etc.

Client Parity

PR #630 Support for server Consumer feature Backoff Lists.

Improvements

Issue #616 / PR #617 Support for timeout propagation in async requests
PR #630 Surfaced delay for nak requests
PR #631 Tune kv subscribe supported functions keys / history / purge
PR #634 Added client side limit checks option to allow turning off client side checks which forces check to server. Default behavior is the same.
PR #635 Improve subscription creation with existing durable to be smarter when comparing provided configuration with server configuration.

Bug Fixes

Issue #621 / PR #622 Fixed kv key with dot as part of the key

Documentation etc.

PR #612 Version change and miscellaneous documentation.
PR #629 Rate Limit is bytes per second (bps) not messages per second.