Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-5121

Relax the CMAP documentation requirement for durations in events

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 5.0.0
    • Affects Version/s: None
    • Component/s: CMAP
    • None
    • Hide

      DRIVERS-2707:
      Update the driver implementation and documentation of CMAP event durations according to the specification changes in https://github.com/mongodb/specifications/pull/1455.

      Show
      DRIVERS-2707 : Update the driver implementation and documentation of CMAP event durations according to the specification changes in https://github.com/mongodb/specifications/pull/1455 .
    • Minor Change
    • Needed
    • Hide

      Let's mention in What's new the following changes:

      • The elapsed time reported via `com.mongodb.event.ConnectionReadyEvent.getElapsedTime` now includes the time to deliver `com.mongodb.event.ConnectionCreatedEvent`, which is the execution duration of the method `com.mongodb.event.ConnectionPoolListener.connectionCreated` on all relevant listeners.
      • The elapsed time reported via `com.mongodb.event.ConnectionCheckedOutEvent`/`ConnectionCheckOutFailedEvent.getElapsedTime` now includes the time to deliver `com.mongodb.event.ConnectionCheckOutStartedEvent`, which is the execution duration of the method `com.mongodb.eventConnectionPoolListener.connectionCheckOutStarted` on all relevant listeners.

      This change is non-breaking because the previous behavior was documented as being subject to change.

      Show
      Let's mention in What's new the following changes: The elapsed time reported via `com.mongodb.event.ConnectionReadyEvent.getElapsedTime` now includes the time to deliver `com.mongodb.event.ConnectionCreatedEvent`, which is the execution duration of the method `com.mongodb.event.ConnectionPoolListener.connectionCreated` on all relevant listeners. The elapsed time reported via `com.mongodb.event.ConnectionCheckedOutEvent`/`ConnectionCheckOutFailedEvent.getElapsedTime` now includes the time to deliver `com.mongodb.event.ConnectionCheckOutStartedEvent`, which is the execution duration of the method `com.mongodb.eventConnectionPoolListener.connectionCheckOutStarted` on all relevant listeners. This change is non-breaking because the previous behavior was documented as being subject to change.

      This ticket was split from DRIVERS-2707, please see that ticket for a detailed description.

            Assignee:
            valentin.kovalenko@mongodb.com Valentin Kavalenka
            Reporter:
            dbeng-pm-bot TPM Jira Automations Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: