Skip to content

Database

To report bugs, please use our SERVER JIRA project.

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

28 results found

  1. Raise maximum BSON document size bigger than 16 MB

    Per https://www.mongodb.com/docs/manual/reference/limits/#:~:text=The%20maximum%20BSON%20document%20size,MongoDB%20provides%20the%20GridFS%20API, maximum BSON document size is 16 MB. I would like to request this to support bigger sizes like 32 MB, 64 MB or even bigger.

    95 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

    22 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)
  2. How to limit the number of document updates?

    Hi
    I want to limit the number of document updates in one command.

    for example

    db.users.updateMany(
    <filter>,
    <update>,
    {
    limit : 100
    }
    );

    https://www.mongodb.com/community/forums/t/how-to-limit-the-number-of-document-updates/102204/3

    25 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  ·  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)
  3. Release notes with urgency and risk

    Provide MongoDB customers/users with an understandable release notes, especially for bugfixes.
    What are the risks this bugfix release covers, what is its urgency.

    Right now, release notes are made of MongoDB Jira tickets, which are very detailed and refer to the implementation of MongoDB, and thus cannot be easily understood by end users.

    As a suggestion, release notes could sum up the following data in a simple table:
    - Nature of impact
    -> data corruption: yes/no
    -> downtime: of a single node / of the whole cluster / on a subset of requests / etc
    - Context of impact

    11 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

    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)
  4. 4 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  ·  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)
  5. connection

    Hi,
    it will be greatly appreciated to have an option to control the connections number when choosing an instance.
    M30 is just what we need except for the connections number
    we have around ~2.5k and max is 3k it would help a lot to have an option to increase just the connections number, so we wont need to move to M40

    3 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

    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)
  6. Collection which stores last login date_time for the users

    Are you please able to store the last login date_time for the users which exist either in admin database or $external database in a collection of admin database of that cluster or opsmanager database which manages the clusters?

    I have a requirement at my end - is to find the users who havent logged in for 60 days, , their roles to be revoked. And, ultimately delete the users who dont have any roles attached after a fixed period of time.

    I do undertsnad you store the login details in audit logs. But that would be a tedious process at…

    3 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

    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)
  7. TTL Support within a document

    The current TTL implementation where documents can expire after a certain amount of time is extremely useful, especially because of its robustness in terms of if the db crashes.

    I would love for this to be extended upon with the ability to allow data within a document to expire after a set time. So for example, if you add data to a document you could set that data and that data only to expire with its own time to live value

    3 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

    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)
  8. Support newer versions of JSON Schema in validation to be able to use the "if", "then", "else" and "const" keywords

    Currently there is no way to have conditional schema validators because you can't use the "const" keyword in a "oneOf" or the "if", "then" and "else" keywords.

    3 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

    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)
  9. Providing connection details with username for real time connection monitoring.

    Currently, mongd.log provides connection details like remote IP, source port with authentication information but doesn't provide the connection is in active state or not.
    serverStatus() only provides number of current and active connections.

    Example:

    10.0.0.100:12345 - username active
    10.0.0.101:12346 - username idle

    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  ·  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)
  10. Include or flag nodes seen more than once / duplicates when traversing with $graphLookup

    When traversing a graph with $graphLookup, we suppress duplicates (in cases of cycles). It would be useful to have an option to include a flag indicating a node that caused the traversal to stop due to duplication.

    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  ·  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)
  11. We need to be able to use $[<identifier>] and "$setOnInsert" in the same command

    I want to be able to have a maintain array of counters for a user through a single update statement. If the document containing array of counters does not exist, I want to add it. If it does exist, I want to increment the counter

    For example, this command

    db.inboxItemCounts.updateOne(
    // filter
    {
    "userId": userDoc.userId
    },
    // update
    {
    "$setOnInsert": {
    "userId": userDoc.userId,
    "fromUserSummary": [{
    "userName": fromUserDoc.userName,
    "count": 1
    }]
    },
    // "$inc": incBody,
    "$inc": {
    "fromUserSummary.$[userElement].count": 1
    }
    },
    // options
    {
    "upsert": true,
    "writeConcern": { "w": "majority" },
    "arrayFilters": [
    { "userElement.userName": { $eq: fromUserDoc.userName }}
    ]
    }

    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

    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)
  12. Preserve field order in $merge

    Filed on behalf of https://jira.mongodb.org/browse/SERVER-63853:

    A variety of formats require strict adherence to the sequence of fields, such as bioinformatics

    Files of such formats are often very large and contain nested structures, so it is convenient to use them as collections. But to keep the data belonging to the above specs, it is necessary to keep the arrangement of the fields. Unfortunately, aggregations with saving results to another DB lose original arrangement.

    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

    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. upgrade src/third_party/gperftools ≥ 2.10

    gperftools new version support new architecture

    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)
  14. Support hex conversion and binary operators in aggregation framework

    The aggregation framework lacks function for HEX <-> Number conversion and binary operations. Such functions are common in almost every programming language.

    Typically and most required operations would be:

    • convert Int/Long to Hex
    • convert Hex to Int/Long
    • Create BinData from Hex string
    • Get Hex string of BinData
    • Binary AND
    • Binary OR
    • Binary XOR
    • Binary NOT (i.e. complement)

    Some of these functions are available in mongo shell or in Bitwise Query Operators but they do not exist in aggregation framework.

    For details see https://jira.mongodb.org/browse/SERVER-55386

    This request becomes more urgent, because starting in MongoDB 8.0, server-side JavaScript functions ($accumulator, $function, $where) are…

    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)
  15. Write parts of database engine in ZIG

    Zig is a zero-dependency, drop-in C/C++ compiler that supports cross-compilation out-of-the-box. Implementing some parts of MongoDB database engine core in ZIG might brings some performance improvements.

    https://ziglang.org/

    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. Self-Managed Computed Collections

    This feature would enable MongoDB to automatically generate common patterns by computing entire collections. A particularly useful application would be the ability to identify duplicate fields within a collection and create a computed collection that groups all possible duplicate together.

    Sometimes, a field is duplicated between two documents, while another field in the same document is duplicated across seven other documents. Each of these seven documents might have fields that are duplicated in yet other documents, leading to a vast iteration in search of possibilities.

    Having MongoDB abstract all this logic in a performant manner to create computed collections would…

    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)
  17. Make account connections stable

    My account is stuck in "We are deploying your changes (current action: configuring MongoDB)" endless loop for the entire eveing and I cannot finish my project for tomorrow. Cannot connect to my database even with a saved IP.
    Yes it's a free account, but this is not a way to just kill any possibility to connect to a simple database. This is a flop

    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)
  18. no puedo crear bases de datos

    quiero elegir un servicio para crear la base de datos y no me deja en cuanto selecciono free o cualquier otro me envia al overview y nunca puedo terminar de apretar el boton para crear la base de datos

    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)
  19. placement of mongosh,mongo tools and mongo binary inside core bin

    Hi Team,
    Hope you are doing great!
    Didn't understand the purpose of keeping mongosh,mongo tools and mongo binary separately, can't this be place in a single rpm/tar file so that it can be easy the installation process.
    As per the current :
    Mongo binary location :

    /var/lib/mongodb-mms-automation/mongodb-linux-x86_64-6.0.8-ent/bin

    Mongo Tools location :

    /var/lib/mongodb-mms-automation/mongodb-database-tools-linux-x86_64-100.7.4/bin

    Mongosh location :

    need to keep this file in separate location and access the mongodh. mongosh-1.10.1-linux-x64.tgz

    Thank you

    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)
  20. Exclude PDB files from installation

    mongod.pdb is nearly 1.0GB, mongos.pdb - 0.5GB

    Since these fils are not necessary for the server to function properly, they should be optional, e.g. provide a checkbox to exclude them during installation.

    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)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base