Skip to content

DOCS-15368 - Clarify UUID changes #402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 15, 2023
Merged

DOCS-15368 - Clarify UUID changes #402

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
43b17c9
wip
mongoKart May 10, 2023
7faf0b6
cc feedback
mongoKart May 15, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions source/upgrade.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,16 @@ Version 4.0 Breaking Changes
UUID values must explicitly specify which representation to use. You can
specify the representation in the ``uuidRepresentation`` property of
``MongoClientSettings``.

The UUID representation that you specify strictly controls how the driver
decodes UUIDs. In previous versions of the driver, if you specified the
``JAVA_LEGACY`` representation, the driver would decode binary objects
of subtypes 3 and 4 as UUIDs. In version 4.0, the ``JAVA_LEGACY``
representation works only with subtype 3.

For a list of members in the ``UuidRepresentation`` enum, see the
`API documentation. <https://http://mongodb.github.io/mongo-java-driver/4.0/apidocs/bson/org/bson/UuidRepresentation.html>`__

- The connection pool no longer restricts the number of wait queue threads
or asynchronous tasks that require a connection to MongoDB. The
application should throttle requests as necessary rather than depend on
Expand Down