Skip to content

MongoDB Go Driver 1.13.0
Compare
Choose a tag to compare
@prestonvasquez prestonvasquez released this 08 Nov 19:59
· 76 commits to v1 since this release
v1.13.0
This tag was signed with the committer’s verified signature.
prestonvasquez Preston Vasquez
GPG key ID: 5236FA2B097952C0
Learn about vigilant mode.
01cc2a2
This commit was signed with the committer’s verified signature.
prestonvasquez Preston Vasquez
GPG key ID: 5236FA2B097952C0
Learn about vigilant mode.

⚠️ Retracted

v1.13.0 has been retracted because the Github tag was modified, leading to a security error when dowloading the Go module. The original tag does not include all changes intended for v1.13.0 and should not be used.

Please use version 1.13.1 or higher.

The MongoDB Go Driver Team is pleased to release version 1.13.0 of the official Go driver.

Release Notes

This release enhances logging, search index management, and command events. This release also introduces smarter server selection for sharded clusters, optimizing retry selection. Additionally, we streamline resource usage on FaaS platforms by disabling streaming SDAM and introduce the serverMonitoringMode=stream/poll/auto URI option.

Logging

In this release, we add logging for server selection and SDAM (Server Discovery and Monitoring). See the Go Driver logging documentation for usage.

Search Index Management Helpers

New mongo.Collection methods have been added to support search index management. For more information on search indexes, see the documentation here.

Users can create and manage search indexes programmatically. This update provides more flexibility and a smoother user experience, allowing you to define your search index within your code.

Include DatabaseName in Command Events

DatabaseName is now returned by event.CommandStartedEvent and event.CommandFinishedEvent. This field will also be included in the command logging analogues. This addition will improve performance for users needing to keep a thread-safe map to maintain command-database relations, whereas now such a map can be deprecated.

Possible Retries to Alternate Mongos for Read/Write

In sharded MongoDB cluster deployments, it's essential to avoid repeatedly selecting a failing mongos instance. Currently, the driver randomly selects a mongos for each operation, which can lead to retrying failed operations with the same problematic mongos. This enhancement introduces smarter server selection for sharded topologies:

  1. The driver will distinguish between the initial attempt and a retry.
  2. It will remember the server used for the initial attempt.
  3. When retrying, if multiple eligible mongos servers are available, the driver will select randomly from the healthy ones, excluding the previously used server.

The driver can assess mongos health before attempting a query and exclude unhealthy mongos from selection.

Transition to Polling Monitoring in FaaS Environments

In this release, we make important changes to enhance performance and flexibility. By default, streaming SDAM is now disabled on AWS Lambda and similar FaaS platforms, ensuring efficient resource utilization. We also introduce the serverMonitoringMode=stream/poll/auto URI option to give you greater control over monitoring modes. To improve client behavior, we mandate that clients refrain from using dedicated connections to measure Round-Trip Time (RTT) when employing the polling protocol. These updates aim to provide a more versatile and efficient experience for users.

For a full list of tickets included in this release, please see the links below:

Full Changelog: v1.12.2...1.13.0

Documentation for the Go driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. Questions and inquiries can be asked on the MongoDB Developer Community. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go driver is greatly appreciated!

Assets 2