Skip to content

Database

To report bugs, please use our SERVER JIRA project.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

320 results found

  1. Support for Transaction Savepoints (Nested Transactions)

    The ability to partially rollback transactions to a specified point.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Transactions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Allow collection collation to be editable

    Collation of a collection can be set at creation time only. It would be useful to edit these fields to avoid creating an entire new collection and copying the collection over.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Add Event Stream Features (Apache Kafka, NATS Streaming)

    I thought it would be great if mongodb can support an event streaming(event bus) feature.
    Existing popular event streaming services(AWS Kinesis, NATS Streaming, Apache Kafka) can persist data which is somewhat like a database.

    Its great for debugging, data logging for later uses such as machine learning. Since I can see the full flow of the data and its changes.

    But there are two downside with most even streaming services.
    1. Its very difficult to query the data.
    2. "Eventual Consistency" issue when dealing programmatic errors(bugs). Most event streams have this nice feature, which keeps sending the same event to…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Performance problem with compound index using doubles, with range filtering

    It looks like there may be a problem when using doubles in a compound index and using range-test filters against all of them in a query.
    The problem we see from the explain plans is that far more keys are being examined that there should be and this leads to poor performance.
    If we switch to using a similar setup but with integers instead, we don’t see the problem.

    See the second part of this ticket for full details

    https://support.mongodb.com/case/00659614

    We have a document that looks like this –

    {
    "id" : ObjectId("5e2ab24eca314f10b486d827"),
    "attributes" : [
    {
    "attributeCode" :

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Too many keys in 2dsphere index when used on geoJson within arrays

    Mongo support have asked me to raise this bug as an improvement idea because they see it as an edge case.
    The issue is here and includes more details:

    https://support.mongodb.com/case/00659614

    In summary, if you have a geoJson sub document that sits within an array, and you index it using the 2dspehere index, you get keys duplicated for every element in the array.

    For example, if you have geoJson that represents a big 4,500 vertex polygon, and you put it within an array element, if the array has only one element I see 20 keys generated, which is good. But if…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Making Elections Faster.

    Election is an expensive operation. We can avoid the elections if we can enforce some priority-based ordering on who shall become primary if the current primary fails.
    Specifically, we can keep a node with second highest priority in the data center of the most preferred primary. Usually, the network failures within the data centers are less probable than across the data centers. So, it is reasonable to believe that if the second preferred member loses the contact with current primary, it is the primary node which has failed and not the network. As a supplement, we can also have redundant…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Decouple "insert" privilege from implicit collection creation

    MongoDB currently allows a user with the insert privilege on a database to implicitly create a new collection by inserting into it — even if the user lacks the createCollection privilege. This behavior makes it difficult to enforce strict access control policies, particularly in security-conscious or regulated environments.

    In contrast, traditional SQL databases like PostgreSQL and MySQL enforce a clear separation:

    The INSERT privilege applies only to existing tables.
    A separate CREATE privilege is required to define new tables.

    We request that MongoDB introduce the ability to decouple insert from implicit collection creation, such as:

    A new action like "insertExistingOnly",…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Administration  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Models  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Provide a dictionary for matched/modified/deleted counts for bulk writes

    Current bulk write operations provide only aggregated counts that look like this:

    {
    acknowledged: true,
    insertedCount: 0,
    insertedIds: {},
    matchedCount: 2,
    modifiedCount: 2,
    deletedCount: 0,
    upsertedCount: 0,
    upsertedIds: {}
    }

    All these operations are processed individually by the server, even if out of order, meaning that the current Mongo DB code aggregates these individual counts in order to present them in the structure above.

    This aggregation, however, makes it impossible to use bulk writes in the same way single updates and deletes can be performed, which significantly slows down mass updates.

    Consider updates of versioned documents - one can issue…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Performance  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. x509 Authentication Supports Multiple CA's

    I work for a large entity with a complicated security certificate structure where we are unable to create certs with specific CA's but rather they are issued to us by request and thus we don't always have control over the root or intermediate CA in the chain.
    We have a situation where server certificates are signed with one CA but client certificates are signed with a different CA. All the CA's are installed and trusted in our Windows certificate store, but the current limitation of Mongo is it only supports a single CA.
    Would it be possible for Mongo to…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Certificate "friendlyName" (windows system certificate store)

    mongod.exe:
    currently there is only support for "subject" and "thumbprint" to select the certificate from the windows certificate store.
    Is there a plan to implement the "friendly name" of the certificate as well?

    example mongod.cfg:
    ..
    tls:
    mode: requireTLS
    certificateSelector: friendlyname=FRIENDLY-NAME

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. deleteMany() execution automatically disable the balancer on sharded clusters

    deleteMany() execution automatically disable the balancer on sharded clusters

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Sharding  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Execute $group on shardPart instead of mergerPart

    Basically what is described here: https://www.mongodb.com/community/forums/t/how-to-enforce-mongodb-to-execute-group-on-shardpart-of-the-execution-plan/267560

    When running covered count queries that could be aggregated independently on the shards, there is still a lot of overhead due to the fact that shards have to report documents with _id to mongos

    It looks like this is happening for count queries that use $limit stage, but not for count queries without it

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Performance  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Support for proxy protocol on mongod

    Hi,

    I have mongodb database server running as a container on kubernetes and i have istio as ingress, but i need proxy protocol in order to preserve source ip, because without proxy protocol the client ip that arrives in mongodb server is the ip from the istio ingress gateway.

    I know mongos already supports it for sharded clusters, but would be very helpfully if mongod could support proxy protocol as well.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Option Renaming Time Series Collections

    Ability to rename TS collection . We need it for migration history data to TS without downtime during conversion.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time Series  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Support retrieving all connections info from clients to mongodb

    Support retrieving all connections info from clients to mongodb, not just those running commands returned by currentOp(). OS command netstat can return all ip info, but it does not contain the relation ino between ip and database such database name and user. It's a common function in relation database, e.g. 'show processlist' command in mysql. And it's useful when we try to migrate to a new MongoDB cluster, we need to find out all the clients connected to the original mongodb.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Administration  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Multiple unique single indexes in sharded collections

    MongoDB sharded collection can only have one unique index which is the shard key. However, in real applications, one might need more than one single unique index. "Proxy" collections suggested in https://www.mongodb.com/docs/manual/tutorial/unique-constraints-on-arbitrary-fields/ has 3 issues:

    1. The most important one is that it does not enforce a one-to-one relationship between the main document and the proxy document. So if I follow the example in the link, two different emails can have the same parentid. You can add a unique single index on parentid but that will not work if the proxy collection is sharded.

    2. If I want to add…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Indexes  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Is there any limitation on size of query in pipeline (character in query, not data)

    I have an aggregate query, when the character in pipeline over 21066 character, the result return wrong format that the pipeline expected. So I wonder is there any limitation on size of query in pipeline?

    My case is:
    Query: [
    "$match":{"profileID": {"$in": ['', .....]}},
    {"$group":{"_id":"$profileID","materialLevel2":{"$sum":{"$cond":[{"$and":[{"$eq":["$expenseL2","true"]},{"$eq":["$expenseL3","false"]},{"$eq":["$expenseL4","false"]}]},1,0]}},"materialLevel3":{"$sum":{"$cond":[{"$and":[{"$eq":["$expenseL3","true"]},{"$eq":["$expenseL4","false"]}]},1,0]}},"materialLevel4":{"$sum":{"$cond":[{"$eq":["$expenseL4","true"]},1,0]}}}}
    ]

    The true result is:
    [{
    "_id" : "000.03.50.H29",
    "materialLevel2" : 1.0,
    "materialLevel3" : 1.0,
    "materialLevel4" : 2.0
    },...]

    But when the length of query greater than 21066 character, the result of query is:

    [{
    "profileID" : "00.00.00.PTT",
    "expenseL2" : "true",
    "expenseL3" : "true",
    "expenseL4" : "false"
    },....]

    Thanks!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Support concise correlated queries for $graphLookUp

    Similar to $lookUp, support concise correlated queries for $graphLookUp.

    It would allow adding a $project stage to reduce overhead.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base