Drivers
77 results found
-
Allow to set default maxTimeMS for all cursors
By default, a cursor has no maxTimeMS.
We want to be able to set the default maxTimeMS so all cursors have it set. The current Java driver does not allow to set that default and each cursor needs it manually specified. I.e. a cursor factory or default options would be great.
Alternatively, it would also be great to have this as an option on the cluster itself.
16 votes -
Add a function for determining if a connection object is still healthy
If an application needs to cache database connections to MongoDB. It would be helpful to have a function to call when retrieving a cached database connection. This function would ensure the connection is healthy before use. It could just return a boolean and allow the client application to handle a bad connection accordingly.
Using a disconnected event handler is not always reliable especially with FaaS serverless functions.
5 votes -
Provide an event for collecting schema validation, with validation Action as a warning.
We are looking for a method for collecting data related to scheme validation issues for logging in the c# driver. Currently, we can set schema validation to error and capture the issue using mongo write exceptions. However, we don't want to restrict the data write, but rather capture the invalid document in the logs to determine the root cause.
1 vote -
Add support for tlsAllowInvalidCertificates
We use mongodb replicaset with encryption in-flight enabled (tls=true), but we don't require client certificates. For mongosh and c# drivers there is a parameter tlsAllowInvalidCertificates which let us DONT use any certificates including root CA certificate.
But java driver does not support this parameter. which creates extra complexity to maintain java applications.
Can we add support of this parameter to java drivers as well ?
1 vote -
Asynchronous variant of MongoDB C Driver
Add async API on the C Driver.
32 votesWe have started a formal investigation on adding async APIs in MongoDB C Driver.
If you have any suggestions or willing to test our prototypes and share feedback, please comment here or reach out to me (rishabh dot bisht at mongodb.com).
-
ODBC drivers for Red Hat systems
As we do not have any ODBC Driver versions available for RedHat OS, we require an ODBC driver compatible with RHEL 8 and above.
1 vote -
Workload Identity Federation Support
Workload Identity Federation is supported since Mongo 7.0 on Atlas. Ruby is still missing from the supported drivers though https://www.mongodb.com/docs/atlas/workload-oidc/#connect-an-application-to-mongodb-with-workload-identity-federation.
Add support to connect using WIF on the ruby-driver.
1 vote -
Atlas SQL - Provide 32-bit ODBC Driver
MongoDB is transitioning away from the BI Connector for Atlas to Atlas SQL. The BI Connector will be deprecated by June 2025.
Moving to Atlas SQL ODBC driver is fine, however the ODBC driver is available only for 64-bit.
I know we are in 2024 but there are still 32-bit applications, e.g. our MS-Office is still 32-bit. If I like to query MongoDB in Excel or Access, I need a 32-bit ODBC driver to do that.
1 vote -
getMore retries support for autoscalling feature
its not possible use https://motor.readthedocs.io/en/stable/api-tornado/cursors.html#motor.motor_tornado.MotorCursor.to_list and https://pymongo.readthedocs.io/en/stable/api/pymongo/cursor.html#pymongo.cursor.Cursor with autoscalling feature :(
https://www.mongodb.com/docs/manual/core/retryable-reads/#unsupported-read-operations
2 votes -
Support TagWithCallSite and TagWith with EF Core Provider
It'd be good to support TagWithCallSite and TagWith so it's easier to figure out where the queries came from. The "tag" could be put in the query option comments so that it can be used when profiling and with otel integrations.
1 vote -
Make driver aware of Autoscaling
Driver not aware of autoscaling (topology changes)
This is related to https://support.mongodb.com/case/01186544. We are experiencing exceptions when autoscaling is supposed to work flawlessly. The problem seems to be that the driver checks for a heartbeat every few seconds but fails to do so under heavy bursts of workloads, which we are currently facing.
When autoscaling kicks in, there should be a possibility to make the nodes aware that they have been scaled, so that when they communicate with the driver, they provide this information back to the driver. The driver would then explore the new topology first before throwing…
5 votes -
Golang Driver - MongoDB-AWS Authentication support for any short-lived STS token
The Golang driver supports "MONGODB-AWS" AuthMechanism when you have:
- a
AWS_WEB_IDENTITY_TOKEN_FILEandROLE_ARNenvironment variable, eg when supplied by IAM Roles for Service Accounts (IRSA), typical in Kubernetes clusters (assume_role_provider) - a
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIenvironment variable, typical in AWS Elastic Container Service (ECS) clusters (ecs_provider) - an AWS EC2 Instance Profile attached, such as when running on an EC2 instance with the Instance Metadata Service enabled. (
ec2_provider) - IAM User or STS keys - either directly as environment variables, or via directly setting on a Credential object (
env_providerandstatic_provider)
These are all in the mongo-go-driver…
1 vote - a
-
Take possible SerialName annotation into account for the query DSL (Kotlin)
Hey,
I'm talking about the kotlin-driver (there was no kotlin selectable in the dropdown, so I chose "Java" since the kotlin driver is based on the java driver).
When using the kotlin-driver with kotlinx.serialization it's a bit complicated to write refactoring-safe queries, because when using the KProperty.name reference like in the examples of the documentation a possible
@SerialNameannotation is not considered.I'd like an API matching what KMongo provided that you can just reference the KPropery, and the driver under the hood decides whether to choose just the
nameor the value of a possible SerialName annotation.3 votes -
Add support for new pagination feature
Please add support for new pagination features explained here:
https://www.mongodb.com/docs/atlas/atlas-search/paginate-results/1 vote -
Hibernate and MongoDB
Hibernate OGM is not currently supported. It would be great to use Hibernate with MongoDB.
1 vote -
Support for MongoDB Package in Edge Computing Environments
The increasing adoption of edge computing and serverless architectures necessitates compatible database solutions. The MongoDB Node.js package currently faces compatibility challenges in edge environments, such as Vercel Edge Functions, due to its reliance on certain Node.js APIs and JavaScript features unsupported in edge runtimes.
Discussions on platforms like Stack Overflow and GitHub highlight the need for a MongoDB solution tailored for edge computing. Although the MongoDB Data API offers a potential workaround, it lacks the full functionality and efficiency of the native MongoDB driver when used in edge contexts.
I propose the development of an edge-optimized MongoDB package or library…
1 vote -
.NET 6.0 support for Entity Framework driver
The pre-release version of the EF support in C# driver is only published for .NET 7.0 while the LTS version of .NET is 6.0 and many vendors use (and will use it) for a long time. The roadmap from https://github.com/mongodb/mongo-efcore-provider#limitations–roadmap doesn't mention support for any other .NET versions.
The support of .NET 6.0 would potentially increase adoption and user base.
1 vote -
Improve MongoDB Kotlin driver to match Kmongo or Realm
Having tested both Realms and KMongo i can say that the MongoDB Kotlin driver is lacking a lot when it comes to idiomatic kotlin.
First of all, requiring Strings and not accepting KProperty<T> forcing people to type Foo::bar.name is something that should have never made past v1.0
Second of all, the kotlin driver doesnt solve any of the issues that KMongo had - in fact, its a downgrade from KMongo. Update doesnt accept Kotin objects as a parameter something that is done by Realms.In order for MongoDB Kotlin driver to even be considered usable it needs to be better…
2 votes -
Add Date support to pymongoarrow
pymongoarrow already supports datetime but that is not ideal to store partitioned values. I assume we would ideally store dates as BSON Date in MongoDB and then get back a Parquet Date. Y'all already support many data types (https://github.com/mongodb-labs/mongo-arrow/blob/main/bindings/python/docs/source/data_types.rst). It's just that partitioning by date is very useful for us.
1 vote -
Move Client Model into a separate Maven artifact
Currently there's a large client library: mongodb-driver-core. My suggestion is to split it into 2 - moving out the com.mongodb.client.model package into a separate module.
The reason I need (and hopefully it's not just me) is because I'm trying to work with a software that allows passing a MongoDB JSON query as part of the request. But it then passes it to the actual Mongo instance itself. We don't have to connect to Mongo ourselves. It would be nice to have a library with all the eq() and the rest of the functions that we could use to then serialize…
1 vote
- Don't see your idea?