Skip to content

[JAVA] Relax the CMAP documentation requirement for durations in events #501

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.

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 3 commits into from
Jan 18, 2024
Merged
Changes from all commits
Commits
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
12 changes: 12 additions & 0 deletions source/whats-new.txt
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,18 @@ The 5.0 driver release introduces the following features:
``isNumber()`` and ``asNumber()`` methods match the Java responses for
equivalent ``Decimal128`` values.

- The ``getElapsedTime()`` method on ``com.mongodb.event.ConnectionReadyEvent``
includes the time taken to deliver the ``ConnectionCreatedEvent``. That is,
the time returned includes the duration of the
``com.mongodb.event.ConnectionPoolListener.connectionCreated()`` method.

The ``getElapsedTime()`` methods on
``com.mongodb.event.ConnectionCheckedOutFailedEvent`` and
``com.mongodb.event.ConnectionCheckedOutEvent`` include the time taken to
deliver the ``com.mongodb.event.ConnectionCheckOutStartedEvent``. That is, the
time returned includes the duration of the
``com.mongodb.eventConnectionPoolListener.connectionCheckOutStarted()`` method.

- The ``org.mongodb.scala.Observable.completeWithUnit()`` method is deprecated.
This relates to a :ref:`breaking change about Observables in this version
<java-breaking-changes-v5.0-observables>`.
Expand Down