Drivers
79 results found
-
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 -
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 -
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 -
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 -
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 -
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 -
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 -
.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 -
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 -
JVM Driver - Implement CRaC interfaces into connection pool to allow for database access in an AWS Lambda function startup with SnapStart
See AWS Docs here - https://docs.aws.amazon.com/lambda/latest/dg/snapstart-runtime-hooks.html
Essentially, the pool should disconnect all open connections when saving state to prevent accidental connection reuse.
1 vote -
Support for FilterDefinition as part of Atlas Search/$search
Allow the Search Function to accept a FilterDefinition<T> object and/or a SortDefinition object to do the filtering/sorting as part of the Search routine instead of it being in a unique format only to search.
1 vote -
Closing a closed cursor should not throw
If a cursor is already closed, and
close()
is called, it should quietly do nothing. ThrowingIllegalStateException
is just rude.1 vote -
single-thread pymongo
Hi.
I am using MongoDB Atlas and have recently moved my site to Google App Engine.
GAE supports only limited multithreading and outputs errors about PyMongo.Disabling multi-threading option of PyMongo will help me.
Thanks.
1 vote -
MongoChangeStreamCursor.getResumeToken() should be initialized on open
A newly opened change stream cursor returns null for
getResumeToken()
. This makes fault tolerance cumbersome and full of corner cases during the period before the cursor acquires its resume token, which can take a long time on a quiescent database.There exists a way to cause a change stream cursor to acquire a resume token immediately, even before it sees its first event, by calling
tryNext
. However, this also causes the cursor to block for the polling period (maxAwaitTime
), and shortening the polling period has other adverse effects.Fault tolerance and recovery logic would be significantly…
1 vote -
Support getting connection provider when connecting with aws authentication
It would be helpful if the connect function would support getting one of "@aws-sdk/credential-providers", in case of AWS authentication.
see:
https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/modules/_aws_sdk_credential_providers.html#fromNodeProviderChainReason:
mongo db driver for node js, checks the credentials in specific order, and gives precedence to env. There is no way to override it.
This causes a problem when running from EKS cluster, and using web identity token file.
When my pod needs to access also other AWS resources like S3, and I expose AWS environment variables (like AWSACCESSKEYID, AWSSECRETACCESSKEY), the MongoDB driver takes into account the credentials before the web identity…1 vote -
IDE Plugin
Provide a way for MongoDB users to interact with their data from an IDE
1 vote -
Normalize maximum time in MS parameter name, maxTimeMS vs max_time_ms
Currently, some operations such as aggregate() or count_documents use maxTimeMS as parameter name, but others such as the find(), use max_time_ms, so unless you memorize which method uses which nomenclature, you have to check the docs every time.
This is specially confusing since, for example, find_one() uses max_time_ms but all the find_one_and_...() methods use maxTimeMS.1 vote -
CommandStartedEvent::getCommand() not instance of Explainable
I'm trying to build a verbose mode in our MongoDB wrapper library. I was able to implement debug output leveraging CommandSubscriber interface. This part works.
However what I would also like to do is create support for automatic explaining of queries that are being executed. This is not possible due to inconsistency in MongoDB (php) library.- CommandStartedEvent::getCommand() is not an instance of Explainable interface. It's just a deserialized object. There is no way to fetch the original command object to be able to do explain.
- Neither it is possible to remember such command object when creating it. As these are…
1 vote
- Don't see your idea?