22 results found

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

   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

   2 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

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

   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

   2 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

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

   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

   2 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

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

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

   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

   2 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

6. 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 an exception on write failures.

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

   5 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

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

   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

   2 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

8. 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 @SerialName annotation 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 name or the value of a possible SerialName annotation.

   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

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

10. 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
        $listLocalSessions
    

    Enable auto decryption and change streams in the presence of auto-encryption-settings

    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

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

    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

    2 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. Hibernate and MongoDB

    Hibernate OGM is not currently supported. It would be great to use Hibernate with MongoDB.

    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. 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 into JSON. At the same time I don't need any connection-related classes since on my side I don't really connect to Mongo directly.

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

    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

15. Closing a closed cursor should not throw

    If a cursor is already closed, and close() is called, it should quietly do nothing. Throwing IllegalStateException is just rude.

    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

    1 comment  ·  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

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

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

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

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

20. URI validation

    I was building the URI in a spring configuration file as
    spring.data.mongodb.uri=${MONGODB_URI}/test?retryWrites=true&w=majority

    where MONGODB_URI came from a kubernetes secret (as it contains user & password)

    somehow a new-line had slipped into the kubernetes secret, so the query was effectively asking for "fpos-dev-pl-1.kqybg.mongodb.net\n"

    Besides learning how to correctly configure secrets, I learned in the process that neither Spring nor mongo was validating that spring.data.mongodb.uri was a well-formed URI and the application failed to start with error messages relating to not finding DNS and not being able to resolve the TXT record. This was very confusing.

    The driver should accept a URI parameter (instead of a String) and ensures that it is valid.

    I was building the URI in a spring configuration file as
    spring.data.mongodb.uri=${MONGODB_URI}/test?retryWrites=true&w=majority

    where MONGODB_URI came from a kubernetes secret (as it contains user & password)

    somehow a new-line had slipped into the kubernetes secret, so the query was effectively asking for "fpos-dev-pl-1.kqybg.mongodb.net\n"

    Besides learning how to correctly configure secrets, I learned in the process that neither Spring nor mongo was validating that spring.data.mongodb.uri was a well-formed URI and the application failed to start with error messages relating to not finding DNS and not being able to resolve the TXT record. This was very confusing.

    The driver should accept a URI… 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