You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -34,7 +34,7 @@ The main focus of this release was usability improvements and a streamlined API.
34
34
-[📜 Removal of deprecated functionality](#-removal-of-deprecated-functionality)
35
35
-[Cursor and ChangeStream `stream()` method no longer accepts a transform](#cursor-and-changestream-stream-method-no-longer-accepts-a-transform)
36
36
-[MONGODB-CR AuthMechanism has been removed](#mongodb-cr-authmechanism-has-been-removed)
37
-
-[Internal `ClientMetadata` properties have been removed](#internal-clientmetadata-properties-have-been-removed)
37
+
-[Internal `ClientMetadata` properties have been removed from the public API](#internal-clientmetadata-properties-have-been-removed-from-the-public-api)
-[Assorted deprecated type, class, and option removals](#assorted-deprecated-type-class-and-option-removals)
40
40
-[⚠️ ALL BREAKING CHANGES](#%EF%B8%8F-all-breaking-changes)
@@ -86,7 +86,7 @@ When providing a custom AWS credential provider via the auth mechanism property
86
86
87
87
### Explicitly provided credentials no longer accepted with MONGODB-AWS authentication
88
88
89
-
AWS environments (such as AWS Lambda) do not have credentials that are permanent and expire within a set amount of time. Providing credentials in the URI or options would mandate that those credentials would be valid for the life of the `MongoClient`, which is problematic. With this change, the installed required AWS SDK will now fetch credentials using the environment, endpoints, or a custom credential provider.
89
+
AWS environments (such as AWS Lambda) do not have credentials that are permanent and expire within a set amount of time. Providing credentials in the URI or options would mandate that those credentials would be valid for the life of the `MongoClient`, which is problematic. With this change, the fetching of credentials is fully handled by the installed required AWS SDK.
90
90
91
91
This means that for AWS authentication, all client URIs MUST now be specified as:
92
92
@@ -95,7 +95,9 @@ import { MongoClient } from 'mongodb';
The previous method of providing URI encoded credentials based on the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` directly in the connection string will no longer work.
100
+
99
101
## ⚙️ Error handling improvements
100
102
101
103
### Dropping a collection returns false instead of throwing when NS not found
@@ -118,9 +120,9 @@ The `PoolClearedError` thrown in cases where the connection pool was cleared now
118
120
119
121
## 💥 Misc breaking improvements
120
122
121
-
### Change streams no longer whitelist`$changeStream` stage options
123
+
### Change streams no longer filter`$changeStream` stage options
122
124
123
-
Uses are now able to pass any option to `collection.watch()` and if it is invalid in the `$changeStream` stage of the pipeline the server will error. This is to allow users to provide newly added options quickly that are not in our public types.
125
+
Users can now pass any option to `collection.watch()`. If an option is invalid for the `$changeStream` stage of the pipeline, the server will return an error. This change makes it possible to use newly introduced server options without waiting for them to become available in our public type definitions and eliminates the risk of valid but unrecognized options being silently ignored.
124
126
125
127
### Cursors no longer provide a default `batchSize` of 1000 for `getMore`s
This mechanism has been unsupported as of MongoDB 4.0 and attempting to use it will still raise an error.
177
179
178
-
### Internal `ClientMetadata` properties have been removed
180
+
### Internal `ClientMetadata` properties have been removed from the public API
179
181
180
-
Previous versions of the driver unintentionally made properties used when constructing client metadata public. These properties have now been made internal. The full list of properties is:
182
+
Previous versions of the driver unintentionally exposed the following properties that have now been made internal:
0 commit comments