Drivers
77 results found
-
F# Driver
We would like to use MongoDB with F#. There was a brief of prototype solution archived in github but was abandoned. The project I am talking about is https://github.com/mongodb-labs/mongo-fsharp-driver-prototype/pulse
This is an official request for F# driver.
3 votes -
Create / Update LabVIEW Driver
There seem to not exist any official LabVIEW Drivers / VIs for MongoDB.
There do exist some LabVIEW VIs for MongoDB that work very well based on a C# DLL:
https://github.com/RBXSystems/mongo-labview-driver/tree/master/CSharp/bin.However those only work with older MongoDB Versions and I can`t get them to work with Atlas and the most recent MongoDB Version 4.2, I guess the DLLs need to be updated (and depending on the changes of the API also some of the VIs)
3 votes -
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 -
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 -
Make the Go driver interface based so that it can be easily mocked for unitTests.
Provide interfaces for driver classes that can be used to mock the database for unit tests. Along the lines of what AWS does for its services:
https://aws.amazon.com/blogs/developer/mocking-out-then-aws-sdk-for-go-for-unit-testing/2 votes -
Asynchronous variant of IIdGenerator
We have use cases where IDs assigned to documents are generated by an external service. Communication with the external service is asynchronous. We have created custom IIdGenerator implementations for this purpose, and they work, but unfortunately the IIdGenerator interface is synchronous only. This exposes the known problems with "sync over async" code.
Obviously we could assign the IDs manually and not rely on using an IIdGenerator, but it would be very convenient to have an async variant of the IIdGenerator interface for this use case.
2 votes -
Create a close method on the MongoClient.
I have run into a situation where threads are not being garbage collected and are causing a serious issue. When we create a database for a specific user, we generate the users’ credentials inside of that database with access only to that database. The problem arises when we need to delete the user and database. The user sometime in the past connected to MongoDB using their credentials which leaves behind an open thread to the MongoDB that is logging into MongoDB once a minute with that users’ credentials. We then come along with our Admin user account and delete the…
2 votes -
Better handling of circular reference serialization in Java
Given 2 generic POJOs that include references to each other such as:
package com.example; public class Course { Student _student; public void setStudent(Student student) { _student = student; } public Student getStudent() { return _student; } } package com.example; public class Student { private Course _course; public void setCourse(Course course) { _course = course; } public Course getCourse() { return _course; } }It would be useful to have a configuration mechanism to prevent Maximum serialization depth exceeded exceptions from being thrown.
…package com.example; import com.mongodb.ConnectionString; import com.mongodb.MongoClientSettings; import com.mongodb.client.MongoClient; import com.mongodb.client.MongoClients; import com.mongodb.client.MongoCollection; import com.mongodb.client.MongoDatabase; import org.bson.Document; import org.bson.codecs.configuration.CodecRegistry;2 votes -
2 votes
-
Support authentication credential rotation
MongoDB drivers should provide support for rotating authentication credentials:
- The customer may opt to rotate a specific credential (a password, client keytab, or a re-issued client certificate - when your private key will be the old one or a new one and the certificate will always be updated), or both the username and its credential
- drivers must support authentication hooks/override methods to handle custom logic. For example: when an external vault processes the password change, it will have a delay before the SCRAM / PLAIN password gets changed in the MongoDB Server / LDAP server. The customer-provided code will take…
2 votes -
Add support for directly marshaling arrays and slices to Extended JSON
The Extended JSON encoder does not support encoding arrays and slices by themselves. The decoder does support decoding JSON arrays into slices. Add support for encoding arrays and slices to a JSON array.
2 votes -
Provide a mechanism for specifying default database name in connection string
According to https://jira.mongodb.org/browse/GODRIVER-914 the connection string is only meant to specify the auth database. However, many of the official MongoDB drivers and tools also use the database specified in the connection string as the default if commands are run without specifying a database name.
The Go driver should either mirror this behaviour found in other drivers, or a parameter should be added to the connection string to allow a default database to be explicitly defined.
2 votes -
Expired Transactions failures should be reported more clearly in the driver error message
Long-running transactions may trigger an aborted transaction, but the cause is not clearly communicated by the driver exception message.
Failed: Command insert failed: Transaction 1 has been aborted..
Unhandled exception. MongoDB.Driver.MongoCommandException: Command insert failed: Transaction 1 has been aborted..To reproduce, set a very low timeout:
replicaset:PRIMARY> db.adminCommand( { setParameter: 1, transactionLifetimeLimitSeconds: 1 } )
Then run a long running transaction from the C# driver.
The cause can be confirmed by checking the MongoDB log for a [abortExpiredTransaction]:
replicaset:PRIMARY> show log global
2020-07-31T03:59:49.196+0000 I COMMAND [abortExpiredTransactions] Aborting transaction with txnNumber 1 on session xxxxxx because it has been running for…
2 votes -
CSFLE - Enable automatic decryption of change streams
Currently change streams are disabled when a CSFLE MonogClient() session is used.
This is due to this CSFLE specifications.Mongocryptd will not support “collectionless” aggregation metadata sources, which read metadata that doesn’t pertain to a particular collection. The drivers should not contact mongocryptd for such commands, since they don’t have a particular schema to pass to mongocryptd, so it is the drivers’ ultimate responsibility to return an error to the application for the collectionless aggregation metadata sources:
$currentOp $changeStream for watching a database or the whole cluster $listSessions $listLocalSessionsEnable auto decryption and change streams in the presence of auto-encryption-settings
2 votes -
if drive can deal with DateTime.Date,it will be useful
we offen have this require,we need to compare DateTime field on Date(exclude time),but if use drive compare with DateTime.Date,drive will throw a exception tell us dont support..
db.CheckOns.Find(x => x.RecordTime.Date == new DateTime(2020, 3, 19)).ToList();
//public DateTime RecordTime{get;set}2 votes -
use ConventionPack in aggregate same as find
for example :We want save string value of Enum to database,we set EnumRepresentationConvention Convention.
then we can use it in match. but in aggregate group,it dosent work:public enum Gender { Male,Female}
public class Person
{
public int Age { get; set; }
public Gender Gender { get; set; }
}
[HttpGet("test")]
public object Test()
{
var query=db.database.GetCollection<Person>("persons").Aggregate().Group(x => x.Age,g=>new {
g.Key,
MaleCount=g.Sum(x=>x.Gender==Gender.Male?1:0),
FemaleCount = g.Sum(x => x.Gender == Gender.Female ? 1 : 0),
});
var queryString = query.ToString();
return queryString;
}
//queryString will be: aggregate([{ "$group" : { "id" : "$age", "MaleCount" : { "$sum" : {…2 votes -
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
- Don't see your idea?