Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
GODRIVER-3076Backlog
CSFLE/QE Support for more than 1 KMS provider per type
This ticket was split from {{DRIVERS-2731}}, please see that ticket for a detailed description.
Components
Client Side Encryption
JAVA-5275ClosedFixed
CSFLE/QE Support for more than 1 KMS provider per type
This ticket was split from {{DRIVERS-2731}}, please see that ticket for a detailed description.
Components
Client Side Encryption
Fixed Versions
5.2.0
CSHARP-4892ClosedDone
CSFLE/QE Support for more than 1 KMS provider per type
This ticket was split from {{DRIVERS-2731}}, please see that ticket for a detailed description.
Components
Client Side Encryption
Fixed Versions
3.0.0
NODE-5801ClosedFixed
CSFLE/QE Support for more than 1 KMS provider per type
This ticket was split from {{DRIVERS-2731}}, please see that ticket for a detailed description.
Components
Client Side Encryption
Fixed Versions
6.8.0
PYTHON-4112ClosedFixed
CSFLE/QE Support for more than 1 KMS provider per type
This ticket was split from {{DRIVERS-2731}}, please see that ticket for a detailed description.
Components
Client Side Encryption
Fixed Versions
4.7
GODRIVER-2466Backlog
Convert SDAM integration spec tests to the unified test format
This ticket was split from {{DRIVERS-2366}}, please see that ticket for a detailed description.
GODRIVER-3103ClosedDone
CSFLE/QE KMIP support "delegated" protocol
This ticket was split from {{DRIVERS-2732}}, please see that ticket for a detailed description.
Components
Client Side Encryption
NODE-7739ClosedDone
[Mastra] Bring your own collection (assessment)
Summary: [Mastra] Assess and document BYOC: search existing application data without maintaining a separate copy
h2. TL;DR
Bring your own collection (BYOC) lets Mastra search data already stored in MongoDB, without copying it into a separate Mastra-managed collection or maintaining a synchronization job. Assess the existing feature for security and data safety, then document this simpler workflow and its benefits.
h2. Context
Mastra is a TypeScript framework for building AI agents. Its M
Components
ABX
SERVER-136041ClosedFixed
Add SchemaTypeInfo tests for unusual field paths
{{PathArrayness::canPathBeArray()}} has tests for unusual {{FieldRef}} paths, including empty paths and components, trailing dots, dollar-prefixed names, and excessive depth. {{SchemaTypeInfo::canPathBeArray()}} should have comparable coverage. Embedded nulls should also be tested.
h2. Scope
Add focused {{SchemaTypeInfo}} tests for these paths against both known field types and unknown shapes. Verify that lookup does not throw and that its arrayness result is conservative when the path can
Fixed Versions
9.1.0-rc0
SERVER-134937ClosedFixed
Implement InternalSchemaTypeExpression narrowing
Implement narrowType for InternalSchemaTypeExpression. It carries the same MatcherTypeSet as $type, but uses ElementPath with LeafArrayBehavior::kNoTraversal and NonLeafArrayBehavior::kTraverse.
The expression is generated from $jsonSchema but we can test it directly too.
{x: \{$_internalSchemaType: number}} with x = any -> x is number
{x: \{$not: {$_internalSchemaType: number}}} with x = any -> x is any except number
{x: \{$_internalSchemaType: [number, string]}} with x = any -> x is nu
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-134938ClosedFixed
Implement InternalSchemaObjectMatchExpression narrowing
Implement narrowType for InternalSchemaObjectMatchExpression, which holds a path and a single child expression applied at that path, and uses ElementPath with LeafArrayBehavior::kNoTraversal and NonLeafArrayBehavior::kTraverse. This is how $jsonSchema expresses nested properties, as a child tree rather than a dotted path.
Fixed Versions
9.1.0-rc09.1.0-rc1025
GODRIVER-3638ClosedDone
Prohibit using failpoints on sharded topologies
h3. *Context*
On sharded topologies, failpoints are applied to only a single mongoS. If the driver is connected to multiple mongoS instances, there's a possibility a different mongoS will be selected for a subsequent command. In that case, the failpoint is effectively ignored, leading to a test failure that is extremely difficult to diagnose.
We should prohibit using failpoints on sharded topologies with an override for those tests that specifically need to use failpoints on sharded topologi
SERVER-136271ClosedFixed
Return old value in SizeCountTimestampStore::insert()
Implement API parity with SERVER-122992.
Fixed Versions
9.1.0-rc09.1.0-rc1025
GODRIVER-4208Backlog
Document tradeoffs of minor vs patch release for internal-only features
Questions:
* Should we release internal-only features in minor or patch versions? Why?
* Are internal-only options that can rewrite the command a security risk? Why or why not?
Components
Documentation
GODRIVER-4221Backlog
Operation.Execute retries indefinitely on repeated ReauthenticationRequired (391) after a successful reauthentication
h3. Detailed steps to reproduce the problem?
The [auth spec|https://github.com/mongodb/specifications/blob/master/source/auth/auth.md#reauthentication] says:
{quote}
Drivers MUST immediately attempt a reauthentication on the connection using suitable credentials... This attempt MUST be irrespective of whether the operation is considered retryable.
{quote}
This infinite loop is in Operation.Execute, which every command goes through, and has been on master since GODRIVER-3278. Any operat
Components
Authentication
GODRIVER-3480ClosedGone away
Address CSOT Compliance Issue in Timeout Handling for Cursor Constructors
h3. Detailed steps to reproduce the problem?
The CSOT specifications states the following:
{quote}
If set, drivers MUST apply the timeoutMS option to the initial aggregate operation. Drivers MUST also apply the original timeoutMS value to each next call on the change stream but MUST NOT use it to derive a maxTimeMS field for getMore commands
{quote}
One can verify that the Go Driver does not do this by running the ["timeoutMS applies to full resume attempt in a next call"|https://gith
GODRIVER-4212ClosedDone
mongo-go-driver - PR #2692: Merge release/2.9 into master
[mongodb-drivers-pr-bot[bot]|https://github.com/apps/mongodb-drivers-pr-bot] has created [PR #2692: Merge release/2.9 into master|https://github.com/mongodb/mongo-go-driver/pull/2692] in [mongo-go-driver|https://github.com/mongodb/mongo-go-driver]
SERVER-137554ClosedFixed
Make migration destination backoff after an error before retrying
Fixed Versions
9.1.0-rc09.1.0-rc1025
SERVER-121956ClosedFixed
Adding a new node/shard to a replica may cause "ChangeStreamHistoryLost"
Adding a new node to a replica set and making it primary may cause "ChangeStreamHistoryLost" error when trying to resume from it, because the new node's oplog will neither contain past events nor "initiating set" entry.
This is a known limitation of change streams, but it could be somewhat surprising to the user. We can improve the situation in a several ways:
Option 1: better error diagnostics pointing at this situation, e.g., "your primary does not have the same history as your secondari
Fixed Versions
9.1.0-rc0
SERVER-111828ClosedFixed
Track connections churned due to MaxTimeMs expiration on mongos
In order to provide additional visibility into the impact that not having inline cancellation is having on the server (specifically in sharded clusters), lets add a metric that tracks how many connections are churned by the mongos to evaluate the impact of this cancellation model.
Fixed Versions
9.1.0-rc09.1.0-rc1025