Skip to content

Commit d49ec1d

Browse files
committed
DOCS-15368 - Clarify UUID changes (#402)
(cherry picked from commit b30dc6e)
1 parent ebd0a05 commit d49ec1d

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

source/upgrade.txt

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,16 @@ Version 4.0 Breaking Changes
102102
UUID values must explicitly specify which representation to use. You can
103103
specify the representation in the ``uuidRepresentation`` property of
104104
``MongoClientSettings``.
105+
106+
The UUID representation that you specify strictly controls how the driver
107+
decodes UUIDs. In previous versions of the driver, if you specified the
108+
``JAVA_LEGACY`` representation, the driver would decode binary objects
109+
of subtypes 3 and 4 as UUIDs. In version 4.0, the ``JAVA_LEGACY``
110+
representation works only with subtype 3.
111+
112+
For a list of members in the ``UuidRepresentation`` enum, see the
113+
`API documentation. <https://http://mongodb.github.io/mongo-java-driver/4.0/apidocs/bson/org/bson/UuidRepresentation.html>`__
114+
105115
- The connection pool no longer restricts the number of wait queue threads
106116
or asynchronous tasks that require a connection to MongoDB. The
107117
application should throttle requests as necessary rather than depend on

0 commit comments

Comments
 (0)