Skip to content

Database

To report bugs, please use our SERVER JIRA project.

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

295 results found

  1. Allow parallel migrations to be throttled

    This request is for a tuneable parameter to allow the number of parallel chunk migrations to be limited.

    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)
  2. String Json Parser

    lately, I imported a big CSV file, containing fields with values of Json object in String format, the simplest way to parse those strings to object it was by doing find().forEach( JSON.pase then update) it taken too much time to update the collection the only think that i have could done to reduce the latency is putting write priority to 0 which isn't very advisable with high throughput of updates, I don't really know for sure I'am not the expert here but working with big data demand a lot of cleaning, and not being able to do the cleaning on…

    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  ·  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. TTL expiration on embedded subdocs

    TTL expiration on an embedded subdoc will delete the parent/root doc.

    Provide an option to only delete the subdocument on expiration.

    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  ·  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. Ability to view and track collection wise transactions (read,write,success,failures)

    We have multiple microservices using the same collection and we'd like to track how many calls come from each, and also understand which transactions are successful or not.
    Ultimately this will allow us to understand the MDB usage by each of the microservices.
    [setting verbose logging level to 1 and then using these logs to create a dashboard in Splunk doesn't give us enough granularity]

    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  ·  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. Find all geoJSON points within a large collection of polygons. Reference collection in geoWithin.

    I would like to be able to find all geoJSON points located within a collection of polygons. My personal goal is to find points located within earth's water bodies. The water bodies are located in their own collection while the geoJSON points are located in a separate collection within the same DB. Mongo's geoWithin function only lets me hard code the polygons, but I would like to reference a collection of polygons.

    See https://stackoverflow.com/questions/63162823/mongo-geowithin-error-polygon-coordinates-must-be-an-array

    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  ·  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. More verbose information about compact failures in logs

    Recently we had a compact operation fail, and the mongod logs stated this was due to "eviction pressure" on the server. We have learned that this is a failsafe mechanism built into the compact command, but we would like to have a more verbose explanation of this failure mode in the logs to better understand why it failed and steps to remediate the 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

    planned  ·  0 comments  ·  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. MongoDB emulator

    From a user - A MongoDB in-memory emulator would help development against MongoDB in a completely isolated way. They deploy self contained applications for developers that don't have any external connections other than MongoDB. The customer found a community project, fongo, that does this, but it is not supported and trails development by a few versions. https://github.com/fakemongo/fongo. I would be happy to connect the users with relevant project managers

    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  ·  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. Periodic large bulk insert/update all or nothing with instant switchover

    Provide the ability for orgs to update things like large reference data sets periodically. E.g. an ecommerce site updates its product inventory every night at midnight, where even though the inserts or updates may take say 10 minutes to run and complete, the applications do not see the changes until the bulk update finishes. The problem otherwise is currently, the ecommerce app, in this example, may be reading product data partly from yesterday's data and partly from today's changed data, during the 10 minute run. For consistency the application would ideally want to see data from either before the bulk…

    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  ·  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. Support for wildcards in permission parameters

    Support for wildcards or maybe even regular expressions in the database/collection name of a permission for a custom role.

    We have a multi tennant setup, by storing every customer's data in its own database on the cluster. The applications we build span those databases, but every application has it's own permissions on a collection name bases.

    instead of granting "find" permission to the "products" collection of all databases like "mongodbcom" and "somecompanycom", it would be nice if we coulf configure it like "find" permission to the "products" collection on the database matching /^[a-z]+_[a-z]+$/

    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  ·  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. Notification Alert

    Whenever a document is created within a collection to send a email to the account holder.

    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  ·  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. Validate Window

    In 4.4 with validate being able to run in the background.

    https://docs.mongodb.com/master/reference/method/db.collection.validate/#behavior

    It would be good to have a "validate window" that would cycle though each collection. Similar to the way a balancing window works in sharding.

    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)
  12. Allow validate to use replica tags

    The use case for this is to be able to target a secondaries in different shards.

    If validate accepted tag read preference it could be kicked off from a shell connected to a mongos.

    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)
  13. would be helpful, with the online interface, to be able to bulk import collections

    For those whose corporate firewalls do not allow for mongo client access to the free mongo cloud db, it would be extremely helpful to be able to upload a pre-formatted json collection of documents, rather than entering those documents one at a time.

    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  ·  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. mongo binary utility for slaptest

    Please provide binary for slaptest for Mongo server just like mysqlslap for mysql server. This enables us to test a better index by doing a slap test on server with multiple combinations of indexes by dba itself instead of depending on load tests from application like jmeter load test , soasta load test etc which needs involvement of multiple resources, developers, testers and lot of time.

    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  ·  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. maintenance period per cluster

    There are some times when a maintenance is potentially super disrupting such as when node replacements occur due to AZ rebalancing. It would be nice if we can set the maintenance period per cluster vs per project to be able stagger maintenance periods. so that not every cluster goes under such disruptive maintenance.

    0 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  ·  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)
1 2 11 12 13 15 Next →
  • Don't see your idea?

Feedback and Knowledge Base