Hi,

Sorry if this is in the wrong place for this.

In https://jira.mongodb.org/browse/JAVA-3518 the default UUID representation is changed from JAVA_LEGACY to UNSPECIFIED. This is mentioned in the docs under upgrading to 4.0:

• https://mongodb.github.io/mongo-java-driver/4.0/upgrading/

I would argue that the current wording suggests if you simply set UuidRepresentation back to JAVA_LEGACY then you'd see no behaviour change from 3.12.x.

However as a result of this change decoding has become stricter - 3.12.x with representation JAVA_LEGACY would still merrily decode a subtype 4 binary object as UUID:

https://github.com/mongodb/mongo-java-driver/blob/3.12.x/driver-core/src/main/com/mongodb/DBObjectCodec.java#L369

However in 4.0.x the representation MUST be STANDARD to decode subtype 4 as UUID:

https://github.com/mongodb/mongo-java-driver/blob/4.0.x/driver-core/src/main/com/mongodb/DBObjectCodec.java#L368

I understand the point of this change, I'd just like to suggest rewording the docs to be clear that this isn't a simple change of parameter default value - mixed representations of UUID in a collection will no longer be decoded leniently.

A/C:

As a reader, I understand the differences between using 3.12.x JAVA_LEGACY UUID representation and a 4.x JAVA_LEGACY UUID representation (for example difference in decoding a subtype 4 binary object).

Potential Solution:

Update the Upgrade Driver Version to further discuss the differences between 3.x and 4.x UUID representations.