Drivers
80 results found
-
Asynchronous variant of MongoDB C Driver
Add async API on the C Driver.
33 votesWe are excited to announce the release of amongoc - an asynchronous C driver for MongoDB, now in public preview. This experimental driver aims to provide an efficient, non-blocking interface for MongoDB operations.
Share your feedback on GitHub to help shape its development into a production-ready tool. Your input is crucial, and we can't wait to see what you'll build with amongoc!
Resources
-
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 -
Estimated Filtered Count
Hi,
We are currently using a pattern where we use a find(query).limit(x) and a count(query) with $near to find x results and display the overall count. Using this pattern, we are able to pass the same query to find and count. However that count method was removed in SCALA-517 and replaced by estimatedDocumentCount and countDocuments. The problem is that countDocuments will not work with $near. There is a workaround to use $geowithin with $center/$centerSphere, however this doesn't return the results sorted as $near did. We would like to have the option to pass the same query to count as we…
10 votes -
CSFLE - Encryption of fields within an Array Object instead of whole Array
CSFLE - Can you provide Encryption of fields within an Array Object as part of mongo-crypt library in the future releases. current library encrypts the whole array and we are not able to do queries within the Array object.
10 votes -
Client-Side Automatic Field Encryption - Support contacting keyvault via Sock Proxy
When using Atlas from our application in our Datacenter, we are able to connect to it without issue.
When adding CSFLE, some HTTP calls are made to login on Azure and access the AKV. These HTTP calls must go through a proxy.
7 votes -
csfle support for zOS
Please modify your drivers so our java applications can encrypt and decrypt from the mainframe (zOS) UNIX environment. This missing feature is a road-block to our migration to Atlas.
We have multiple Java applications that run on an IBM mainframe. Those applications read and write into MongoDB collections, like inserting Mainframe data into MongoDB collections. The mongo-crypt driver for CSFLE does not work on the Mainframe UNIX environment.
Company policy states we have to encrypt all PHI/PII data prior to inserting the data into Atlas.
I had opened a support ticket with MongoDB and the final reply was you do…
7 votes -
Create an official Elixir driver
See https://github.com/elixir-lang/elixir and https://elixir-lang.org/
Thank you!7 votes -
It will be helpful to provide Sock Proxy support for our drivers
Some customers have security policy restriction to directly connect to Atlas. So it will be helpful for them to use sock proxy to connect.
6 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 -
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 -
Compressed Fields
When large JSON structures are being stored but don't need to be queryable it may be more performant to handle the compression at the field-level as opposed to the network level (similar to what is described in https://medium.com/idealo-tech-blog/advanced-mongodb-performance-tuning-2ddcd01a27d2).
This would isolate compression and decompression on the client side (unless network compression was used as well), however the compressed field would be persisted as-is (compressed) to the cluster.
5 votes -
official Julia driver
Would love to see an official Julia driver.
5 votes -
Allow custom service names with mongodb+srv URI scheme
We are using DCOS (marathon/mesos) to manage our services. DCOS generates SRV records for our mongos instances under a record that looks like
mongos-mongodb.tcp.marathon.mesos
However, there's currently no way for me to use this because when I provide a connection url likemongodb+srv://mongos-mongodb.tcp.marathon.mesos
the drivers prepend "mongodb.tcp" to the provided url. It's not clear why it's required that the host must start with "mongodb.tcp". Why not let the user specify the actual DNS entry to query?I believe the same issue will exist for multiple orchestration frameworks such as Consul/Nomad and Kubernetes.
5 votes -
add deno driver
(i was forced to select a category so i choose nodejs)
Deno is coming https://deno.land/
From the creator of nodejs. Better than nodejs.
5 votes -
Update PyArrow version required for PyMongoArrow to use with Fireducks
Update PyArrow version to use with Fireducks - right now I want to use these three libraries in one data science project:
- fireducks-1.2.2 (pip install fireducks)
- pyarrow-19.0.1 (pip install pyarrow) <-- required by the Fireducks
- pymongoarrow-1.6.4 (pip install pymongoarrow) <-- it requires pyarrow 18.0.0My pipeline connects to MongoDB through PyMongoArrow, downloads big DataFrames and preprocess them with Fireducks superb optimized vector transformations. I tried to side-step the need for PyMongoArrow with code like the attached function, but the end result differs from just using the PyMongoArrow.
What would be needed to update the PyMongoArrow requirements?
4 votes -
Short-lived AWS EKS token
Native support for short-lived AWS EKS token in MongoDB java driver, with the ability to refresh the key without any application downtime.
4 votes -
4 votes
-
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 -
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…
3 votes -
Dynamic Configuration Changes for Connections
We would like to suggest a feature improvement where connection parameters can be dynamically changed so that no restart of client application infrastructure is needed.
Currently, when changing connection configuration, this usually requires the restart of a considerable number of pods or containers with the unavoidable consequence of a sudden surge in connection attempts.
Our request specifically would be to provide a way for drivers to read both connection string and connection parameters information from a source that can be easily managed and that's not necessarily embedded in the code, and
Drivers should also detect when this configuration has changed…
3 votes
- Don't see your idea?