Important!
This release has been delisted as it does not conform to SemVer standards. The functionality and bug fixes this release introduces will be re-released in the upcoming `v3.2.1`, with the change to default container behavior enabled by an opt-in configuration.
Hi everyone,
We’ve just released NServiceBus.Persistence.CosmosDB 3.2.0.
Important!
When using a default container, and also providing a custom message container extractor, the custom extractor was not used in prior versions due to #899. This has now been fixed.
Code changes and/or storage data migration is required for optimal performance.
Guidance:
Fixed bugs
- #899 When using the outbox, the default container is not overwritten by message container extractors
- #893 Endpoints using the outbox subscribed to the same event will experience concurrency conflicts if sharing the same database and container
Improvements
- #912 Allow for a default synthetic partition key to be used for the outbox record if no custom partition key extractors are needed
How to know if you are affected
You are affected by #899 if:
- you are using the Outbox
- you are specifying a default container
- you are using a container message extractor
You are affected by #893 if:
- you are using the Outbox
- you have multiple subscribers to the same event
- you are not using a partition key extractor and therefore falling back to the default outbox partition key of {messageId} for control messages
Symptoms
For #899, the container from the message extractor will not overwrite the default container as expected.
For #893, the published event will not be delivered to every subscriber and a concurrency conflict error will appear in the logs.
When to upgrade
You should upgrade immediately if you are affected. Otherwise, you should upgrade during your next maintenance window.
Where to get it
You can install NServiceBus.Persistence.CosmosDB 3.2.0 from NuGet.
Please read our release policy for more details.
With thanks,The team in Particular