67 results found

1. Golang Driver - MongoDB-AWS Authentication support for any short-lived STS token

   The Golang driver supports "MONGODB-AWS" AuthMechanism when you have:

   • a AWS_WEB_IDENTITY_TOKEN_FILE and ROLE_ARN environment variable, eg when supplied by IAM Roles for Service Accounts (IRSA), typical in Kubernetes clusters (assume_role_provider)
   • a AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variable, typical in AWS Elastic Container Service (ECS) clusters (ecs_provider)
   • an AWS EC2 Instance Profile attached, such as when running on an EC2 instance with the Instance Metadata Service enabled. (ec2_provider)
   • IAM User or STS keys - either directly as environment variables, or via directly setting on a Credential object (env_provider and static_provider)

   These are all in the mongo-go-driver at https://github.com/mongodb/mongo-go-driver/tree/v1/internal/credproviders

   Token Refreshing is required with short-lived credentials, when you want to maintain a long-lived connection to Mongo. At any time the Mongo Cluster's topology may change (eg due to failover, upgrades, adding extra replicas, etc). With short-lived credentials, they must be renewed before trying to (re)start connections to the Mongo cluster.

   All of the cred providers, except env_provider and static_provider support Token Refreshing.

   This means that a developer who's access to AWS is through short-lived STS tokens via a Federated login (AWS SSO, Okta, etc) are not able to authenticate to Mongo for more than their token's expiry time.

   It also means other methods of authenticating to AWS are not supported.

   This request is to support one of the following:

   A) Provide an sts_token_provider, which can try calling the AWS SDK directly to issue a short-lived token, and refresh it prior to expiry
   B) Provide a way for a consumer of the mongo-go-driver to inject their own credprovider, which can obtain and refresh the token.
   C) Provide a way to set an Expiry time for env_provider and static_provider, and a callback to allow refreshing the token

   My personal preference would be for option A, however this would require including larger sections of the AWS SDK into the mongo-go-driver which may not be ideal for the Mongo team.

   My secondary preference is to allow injecting a custom credprovider. The go driver already has most of the framework for this. awscreds.NewAWSCredentialProvider[1] already has an argument for supplying more credential providers. Unfortunately the caller in mongodbaws.Auth[2] doesn't appear to allow this.

   I believe it should be relatively simple to extend the driver to allow passing in a credprovider, and it would eliminate the need for the mongo-go-driver to include more of the AWS SDK.

   [1] https://github.com/mongodb/mongo-go-driver/blob/v1/x/mongo/driver/auth/creds/awscreds.go#L33
   [2] https://github.com/mongodb/mongo-go-driver/blob/v1/x/mongo/driver/auth/mongodbaws.go#L50

   The Golang driver supports "MONGODB-AWS" AuthMechanism when you have:

   • a AWS_WEB_IDENTITY_TOKEN_FILE and ROLE_ARN environment variable, eg when supplied by IAM Roles for Service Accounts (IRSA), typical in Kubernetes clusters (assume_role_provider)
   • a AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variable, typical in AWS Elastic Container Service (ECS) clusters (ecs_provider)
   • an AWS EC2 Instance Profile attached, such as when running on an EC2 instance with the Instance Metadata Service enabled. (ec2_provider)
   • IAM User or STS keys - either directly as environment variables, or via directly setting on a Credential object (env_provider and static_provider)

   These are all in the mongo-go-driver… 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

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

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

   15 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

3. Support for MongoDB Package in Edge Computing Environments

   The increasing adoption of edge computing and serverless architectures necessitates compatible database solutions. The MongoDB Node.js package currently faces compatibility challenges in edge environments, such as Vercel Edge Functions, due to its reliance on certain Node.js APIs and JavaScript features unsupported in edge runtimes.

   Discussions on platforms like Stack Overflow and GitHub highlight the need for a MongoDB solution tailored for edge computing. Although the MongoDB Data API offers a potential workaround, it lacks the full functionality and efficiency of the native MongoDB driver when used in edge contexts.

   I propose the development of an edge-optimized MongoDB package or library that aligns with the constraints of edge runtimes, minimizing dependency on unsupported APIs and leveraging web-friendly APIs like fetch. This would significantly benefit developers by providing a seamless, efficient way to integrate MongoDB into serverless and edge applications, enhancing performance and user experience.

   This request is supported by community feedback and underscores the importance of evolving MongoDB’s offerings to meet the demands of modern web architectures and serverless computing.

   References:
   * https://github.com/arashsheyda/nuxt-mongoose/issues/32
   * https://stackoverflow.com/questions/75423777/is-there-anyway-to-get-mongodb-to-work-on-vercel-edge-serverless-functions
   * https://github.com/drivly/mongo-fetch

   The increasing adoption of edge computing and serverless architectures necessitates compatible database solutions. The MongoDB Node.js package currently faces compatibility challenges in edge environments, such as Vercel Edge Functions, due to its reliance on certain Node.js APIs and JavaScript features unsupported in edge runtimes.

   Discussions on platforms like Stack Overflow and GitHub highlight the need for a MongoDB solution tailored for edge computing. Although the MongoDB Data API offers a potential workaround, it lacks the full functionality and efficiency of the native MongoDB driver when used in edge contexts.

   I propose the development of an edge-optimized MongoDB package or library… 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

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

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

6. Add Date support to pymongoarrow

   pymongoarrow already supports datetime but that is not ideal to store partitioned values. I assume we would ideally store dates as BSON Date in MongoDB and then get back a Parquet Date. Y'all already support many data types (https://github.com/mongodb-labs/mongo-arrow/blob/main/bindings/python/docs/source/data_types.rst). It's just that partitioning by date is very useful for us.

   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. .NET 6.0 support for Entity Framework driver

   The pre-release version of the EF support in C# driver is only published for .NET 7.0 while the LTS version of .NET is 6.0 and many vendors use (and will use it) for a long time. The roadmap from https://github.com/mongodb/mongo-efcore-provider#limitations–roadmap doesn't mention support for any other .NET versions.

   The support of .NET 6.0 would potentially increase adoption and user base.

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

8. 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 than its community alternative.

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

10. Get Java Database form Kotlin Database

    Please create a function that unwraps the Kotlin MongoDatabase to obtain the corresponding Java MongoDatabase. This is necessary to ensure compatibility with libraries that depend on the old Java MongoDatabase.

    0 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

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

12. Support for FilterDefinition as part of Atlas Search/$search

    Allow the Search Function to accept a FilterDefinition<T> object and/or a SortDefinition object to do the filtering/sorting as part of the Search routine instead of it being in a unique format only to search.

    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

13. Asynchronous variant of MongoDB C Driver

    Add async API on the C Driver.

    26 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  ·  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
    under review  ·  AdminRachelle (Director of Product @ MongoDB, MongoDB) responded

    
    

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

15. single-thread pymongo

    Hi.

    I am using MongoDB Atlas and have recently moved my site to Google App Engine.
    GAE supports only limited multithreading and outputs errors about PyMongo.

    Disabling multi-threading option of PyMongo will help me.

    Thanks.

    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

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

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

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

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