Change default UUID representation from JAVA_LEGACY to UNSPECIFIED #528
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit changes the default BSON representation of java.util.UUID values from JAVA_LEGACY (BSON binary subtype 3 with the Java driver's legacy byte order) to UNSPECIFIED. This forces applications that encode or decode documents from MongoDB that contain java.util.UUID values to explicitly specify the UUID representation that they want to use. Typically, a new application would choose the STANDARD (BSON binary subtype 4) representation, while an existing application upgrading to the 4.0 driver would choose JAVA_LEGACY. Applications that do not use UUID values (preferring ObjectId, for example) are not required to specify the UUID representation. Applications can specify the UUID representation either with the uuidRepresentation connection string parameter or the uuidRepresentation property on MongoClientSettings or MongoClientOptions. JAVA-3518
jyemin
commented
Dec 19, 2019
rozza
requested changes
Dec 19, 2019
bson/src/test/unit/org/bson/codecs/DocumentCodecSpecification.groovy
Outdated
Show resolved
Hide resolved
...onal/com/mongodb/internal/async/client/gridfs/AsyncGridFSBucketSmokeTestSpecification.groovy
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit changes the default BSON representation of java.util.UUID
values from JAVA_LEGACY (BSON binary subtype 3 with the Java driver's
legacy byte order) to UNSPECIFIED.
This forces applications that encode or decode documents from MongoDB that
contain java.util.UUID values to explicitly specify the UUID representation
that they want to use. Typically, a new application would choose the
STANDARD (BSON binary subtype 4) representation, while an existing application
upgrading to the 4.0 driver would choose JAVA_LEGACY. Applications that
do not use UUID values (preferring ObjectId, for example) are not required
to specify the UUID representation.
Applications can specify the UUID representation either with the
uuidRepresentation connection string parameter or the uuidRepresentation
property on MongoClientSettings or MongoClientOptions.
Jira: https://jira.mongodb.org/browse/JAVA-3518
Evergreen: https://evergreen.mongodb.com/version/5dfaced8e3c3317439577e34