Drivers
-
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 -
Have the drivers tell us the cost of network connectivity within a query
Have the drivers tell us 1. total query execution time. 2. how much of total query execution time was network connectivity/latency and 3. how much time was the query on the cluster.
This would then tell the developers the cost of network connectivity because right now there is no easy way to measure network connectivity impact to the overall execution time of the query.
1 vote -
Make The client model serializable
I am working on a mongodb connector for the Apache Flink project - https://flink.apache.org/
Internally, Flink is using java serialization to save the records it is working on in a state which in turn used to recover from failures etc, as well as for passing records between different tasks in the pipeline.
I have noticed the mongodb client model classes are not Serializable for instance, classes such as WriteModel https://github.com/mongodb/mongo-java-driver/blob/master/driver-core/src/main/com/mongodb/client/model/WriteModel.java and its subclasses or the different Options like ReplaceOptions https://github.com/mongodb/mongo-java-driver/blob/master/driver-core/src/main/com/mongodb/client/model/ReplaceOptions.javais there a reason for these classes to not be declared Serializable? Is there a way to contribute to the…
1 vote -
Multiple collection ACID transactions
Currently we can update multiple documents with one query if all documents belong to the same collection as shown below;
dB.collection.bulkWrite([ query1, query2, query3, query4 ])
This feature is wonderful but it is paramount if mongodb can enable us to use this query or something similar to update multiple documents from different collections with the one query instead of having to send and await each query one at a time as is currently the case.
The truth is, mongodb only needs to enable this feature of being able to update multiple documents with one query from different collections and then…
1 vote -
Serve API endpoint for MongoDB Compatibility Matrix
This is a feature request for website API calls/endpoints to retrieve the MongoDB Compatibility matrix for each driver language. For example, NodeJS is located here in HTML format https://docs.mongodb.com/drivers/node/current/compatibility/
It would be helpful to have a programmatic endpoint for the same compat table results. This will help log parsers and aggregators to quickly identify applications and clients that are connecting to deployments with untested or incompatible client drivers.
1 vote -
SnakeCaseElementNameConvention
Please add support for snake case convention. Snake Case is super popular with API designs.
https://mongodb.github.io/mongo-csharp-driver/2.13/reference/bson/mapping/conventions/
1 vote -
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 -
Go Driver: Allow Client Side Field Level Encryption (CSFLE) to use IAM Role credentials credentials with KMS access
In order to get the MongoDB csfle lib to work with AWS KMS, we need to set
the following provider details (IAM user credentials) explicitly: accessKeyId and secretAccessKey.It is common and more secure practice for applications to be able to get temporary credentials using IAM roles which will have accessKeyId, secretAccessKey and sessionToken - https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html.
Currently, the Go Driver does not support sending 'sessionToken' along with provider details.
The libmongocrypt library has this support now - https://github.com/mongodb/libmongocrypt/pull/153.
It would be great if Go driver has this support.
2 votes -
GeoNear support on C# driver
Would be great to have GeoNear support on csharp driver https://docs.mongodb.com/manual/reference/operator/aggregation/geoNear/
1 vote -
Support "default" keyword in MongoDB's implementation of JSON Schema
Without defaults, there is a need to iterate though each property just to check if a default value is needed (most probably this can be easily done on type check). Also without defaults we need to remember checking it both in inserts and updates (for example with $push operator)
1 vote -
Add some casting addon or function based on MongoDB's implementation of JSON Schema
Without casting addons, there is a need to iterate though each property just to check if this value needs some casting (most probably this can be easily done on type check). I´m having special troubles with Date type, as most of the time this type is send as an ISO string, but saved in the DB as a DATE
1 vote -
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 -
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.
2 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 -
Provide a direct download for current versions of driver files/dependencies on the official MongoDB sites
Note: This post was inspired by my attempts to find a direct download for the MongoDB Java driver, but I've left the category as "Unspecified" because it could apply to any driver download for which the official sites say to "Just use Maven/etc"
Right now the documentation for the MongoDB Java driver (https://mongodb.github.io/mongo-java-driver/4.2/driver/getting-started/installation/) indicates that "The recommended way to get started using one of the drivers in your project is with a dependency management system." However, as far as I could tell from my own research, the official MongoDB sites have no official direct download link for the…
1 vote -
geoContain
Dear all,
according to the attached image, I have some documents (in blue, with id from 1 to 5) having a geographic extent and a search area (in yellow).
I need to find all documents where search area is completly inside the document's geometry.
Using different words, I need to find all documents where geometry completly covers the given search area.
In my sample, the geo query should return the document with id 1.
This kind of query has a opposite logic than the $geoWithinCould you provide a $geoContain functionality in the next future?
9 votes -
2 votes
-
Nearest read preference should take account of database load
I understand it only take account of network latency however this node can have high load and would give a poor response. Instead, I wished the driver would contact the more distant network latency node that has less CPU/memory load.
1 vote -
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 -
Create Atlas Search helper method for aggregations in java
Java driver doesn’t include a {{search()}} helper method in the Aggregation class, for facilitating Atlas Search queries.
While it's possible to build a custom pipeline which includes a
{ $ search ... }
stage, a dedicated helper method would be convenient.28 votes
- Don't see your idea?