58 results found

1. 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 talling 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 much simpler if successfully opening a change stream cursor also caused it to have a valid resume token. Corner cases in this kind of recovery logic are particularly tricky to test, and particularly costly if the logic fails in production.

   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 talling 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 much… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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#fromNodeProviderChain

   Reason:
   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 token, and fails to connect as my pod specific user, can’t access Atlas.
   When I don’t expose AWS variables, my pod successfully uses the web identity token and connects to Atals.
   ). We need a way to tell the driver where to take the credentials from, not relying on default precedence order.

   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#fromNodeProviderChain

   Reason:
   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Node.js  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. IDE Plugin

   Provide a way for MongoDB users to interact with their data from an IDE

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Java  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Go  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. 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.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Java  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Python  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. 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 generated within the library itself. See functions of Collection class for example.

   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… more
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  PHP  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C#  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. 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 user from the database and then delete the database. This causes the open thread using the now deleted user to start retrying to login using the now deleted users’ credentials over and over every .015 seconds. Our log file store area, about 30Gb fills up within a day with the MongoDB log spew. We need a way to kill a thread once its job is complete, so we don’t get into these runaway situations. I have read that other MongoDB drivers, namely the Java driver, can close the MongoClient. The C# Driver needs the same functionality desperately.Another option is to have the MongoClient stop the thread after 5 try's when the error coming back is user not found.

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C#  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Generic count property in _WriteResult class

    Hi,

    I'm using a MongoDB as a backend for my API and often come to a case where i want to validate whether I updated, inserted or deleted any records. At the moment I use the deletedcount and machtedcount properties in the DeleteResult and UpdateResult object. To provide a more generic way I thought it may makes sense to provide a new property in the generic WriteResult class called affectedrecords or something like that so you can generic react to the result of your database transaction and maybe return a 404 if nothing was updated, deleted or created.
    Let me know what you think and thanks in advance.

    Hi,

    I'm using a MongoDB as a backend for my API and often come to a case where i want to validate whether I updated, inserted or deleted any records. At the moment I use the deletedcount and machtedcount properties in the DeleteResult and UpdateResult object. To provide a more generic way I thought it may makes sense to provide a new property in the generic WriteResult class called affectedrecords or something like that so you can generic react to the result of your database transaction and maybe return a 404 if nothing was updated, deleted or… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Python  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. 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;
    import org.bson.codecs.pojo.PojoCodecProvider;
    
    import static org.bson.codecs.configuration.CodecRegistries.fromProviders;
    import static org.bson.codecs.configuration.CodecRegistries.fromRegistries;
    
    public class App {
      public static void main(final String[] args) {
        CodecRegistry pojoCodecRegistry = fromProviders(PojoCodecProvider.builder().automatic(true).build());
        CodecRegistry codecRegistry = fromRegistries(MongoClientSettings.getDefaultCodecRegistry(),
        pojoCodecRegistry);
        MongoClientSettings clientSettings = MongoClientSettings.builder()
        .applyConnectionString(new ConnectionString("mongodb://localhost:27017"))
        .codecRegistry(codecRegistry)
        .build();
    
        MongoClient mongoClient = MongoClients.create(clientSettings);
            MongoDatabase database = mongoClient.getDatabase("test");
    
            MongoCollection<Student> students = database.getCollection("students", Student.class);
            MongoCollection<Course> courses = database.getCollection("courses", Course.class);
    
            students.deleteMany(new Document());
            courses.deleteMany(new Document());
    
            Student student = new Student();
            Course course = new Course();
    
            student.setCourse(course);
            course.setStudent(student);
    
            students.insertOne(student);
            courses.insertOne(course);
    
            System.out.println(students.find(new Document()).first());
            System.out.println(courses.find(new Document()).first());
      }
    }
    

    The above would result in the following:

    Exception in thread "main" org.bson.BsonSerializationException: Maximum serialization depth exceeded (does the object being 
    serialized have a circular reference?).
            at org.bson.AbstractBsonWriter.writeStartDocument(AbstractBsonWriter.java:285)
            at com.mongodb.internal.connection.BsonWriterDecorator.writeStartDocument(BsonWriterDecorator.java:48)
            at com.mongodb.internal.connection.LevelCountingBsonWriter.writeStartDocument(LevelCountingBsonWriter.java:42)      
            at com.mongodb.internal.connection.IdHoldingBsonWriter.writeStartDocument(IdHoldingBsonWriter.java:78)
            at org.bson.codecs.pojo.PojoCodecImpl.encode(PojoCodecImpl.java:94)
            at org.bson.codecs.pojo.LazyPojoCodec.encode(LazyPojoCodec.java:47)
            at org.bson.codecs.EncoderContext.encodeWithChildContext(EncoderContext.java:91)
            at org.bson.codecs.pojo.PojoCodecImpl.encodeValue(PojoCodecImpl.java:181)
            at org.bson.codecs.pojo.PojoCodecImpl.encodeProperty(PojoCodecImpl.java:169)
            at org.bson.codecs.pojo.PojoCodecImpl.encode(PojoCodecImpl.java:106)
            at org.bson.codecs.pojo.LazyPojoCodec.encode(LazyPojoCodec.java:47)
            at org.bson.codecs.EncoderContext.encodeWithChildContext(EncoderContext.java:91)
    ....... etc
    

    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;

    … more
    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. 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.java

    is there a reason for these classes to not be declared Serializable? Is there a way to contribute to the Java driver project by opening a PR that addresses this?

    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.java

    is there a reason for these classes to not be declared Serializable? Is there a way to contribute to the… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Java  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. 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 it will certainly be superior to the SQL databases and will get much more market share.

    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… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Unspecified  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Unspecified  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C#  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. 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 not support zOS and to put in this request. (Case number 00802484)

    Here is the error message I shared with MongoDB:
    Exception in thread "main" java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/z/os-s390/libjnidispatch.so) not found in resource path (Ýfile:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/,
    file:/ST/usr/lpp/java/IBM/J8.0/lib/, file:/ST/usr/lpp/java/IBM/J8.0/lib/ext/,
    file:/ST/usr/lpp/java/json/org.json-20120521.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/CDRMigrateAccumsToAtlas.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/bson-4.2.3.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/jna-5.6.0.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/json-20160810.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/logback-classic-1.2.3.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/logback-core-1.2.3.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/mongodb-crypt-1.2.0.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/mongodb-driver-core-4.2.3.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/mongodb-driver-sync-4.2.3.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/recordio.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/slf4j-api-1.7.6.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/vault-java-driver-5.1.0.jar,
    file:/sharedappdev/test/CD/apps/mongopoc/mongo40apps/*.mar¨)
    at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1032)
    at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:988)
    at com.sun.jna.Native.<clinit>(Native.java:195)

    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… more

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Java  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Go  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C#  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Node.js  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close