272 results found

1. Record running queries at the time of a failover

   I recently observed some failovers in a replica set that may have been related to long-running queries. However, since these queries happened only sporadically, it was hard to track them down. Since the queries didn't finish, they weren't present in the logs at the time of the crash.

   It would be useful if it could be possible to somehow capture the long-running queries that were running at the time that something went wrong. I recognize that this is potentially impossible, since once something has gone wrong it can be difficult to do anything.

   We ended up being able to diagnose this by watching the real-time stats tab in Cloud Manager at the right time, though we aren't certain. This suggests that maybe this could be some Atlas feature. I don't know how real-time stats works, but if can run when the user isn't watching it, would it be possible to record slow queries at the time of a failover? I could also imagine this as some server feature, where the server would make some effort to write long-running queries to its logs when it becomes a secondary. There may not be a guarantee that this would work, but in the cases where it did it would be useful.

   I recently observed some failovers in a replica set that may have been related to long-running queries. However, since these queries happened only sporadically, it was hard to track them down. Since the queries didn't finish, they weren't present in the logs at the time of the crash.

   It would be useful if it could be possible to somehow capture the long-running queries that were running at the time that something went wrong. I recognize that this is potentially impossible, since once something has gone wrong it can be difficult to do anything.

   We ended up being able to diagnose… 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  ·  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. Identification of unused/less used collections

   As a DBA I'd like to identify unused collections so that I can remove them to optimize performance.
   As of now there doesn’t seem to be a direct way. One option could be to settup auditing or using logging (e.g. set the slow op timer to 0 so we log everything).
   An other might be to use the collstats command and frequently traverse all collections..

   I'd be happy to get a direct method to show me unused resp. last usage of a collection. Based on DB level or even over all DBs.

   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

   0 comments  ·  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. Create and use db links in Mongodb

   Allow Mongodb to access an external database for:
   1.select identifiers on an external rdbms (ex: postgres, sqls, oracle, ...)
   2.use these identifiers to perform aggregations in Mongodb

   Currently, it is necessary to use a third-party tool that connects to several data sources to perform these actions.
   The idea is to be able to perform these "joins" only in Mongodb CLI.

   Regards,
   Jerome

   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  ·  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. NoTableScan at the collection level

   NoTableScan at the collection level instead of mongod level.

   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

   1 comment  ·  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. Add build for Linux Alpine and Debian

   A build in ARM support (Apple M1) for Alpine Linux (or Debian) is needed to run the mongocryptd process. Currently the official node docker images are available only in Alpine and Debian.

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

6. delete logs number of days old

   In the options for Mongo DB Log Settings, there is only
   Max Percent of Disk
   Total Number of files

   A new option for
   Number of Days to keep

   Would be useful

   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  ·  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. Add expression indexes

   An expression index is one where the value being indexed is the result of an expression, like lower casing a string.

   http://en.wikipedia.org/wiki/Expression_index
   http://www.postgresql.org/docs/8.1/static/indexes-expressional.html

   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  ·  Indexes  ·  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. Deny Network Access to MongoDB Cluster

   To improve network security, please create an option to Deny specific Network Adresses to MongoDB Cluster.

   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  ·  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. Data Replication from one MongoDB Cluster to another MongoDB Cluster

   Create an option for the user to replicate data from one MongoDB Cluster to another MongoDB Cluster inside the account. We don't need to migrate data, I need replicate data from an Production Cluster to an Dev/Test Cluster. Thanks.

   8 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  ·  Replication  ·  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. Support split documents on disk

    As an application's functionality grows, if kept unchecked it is easy for average document sizes to grow simultaneously.

    Large documents can have a significant impact on the performance of MongoDB. However, often the application doesn't actually need the entire document to service a request. Likewise, often queries are sent to MongoDB with a projection, excluding substantial (in terms of byte size) parts of the document.

    MongoDB has no ability to optimise these projections (except for covered queries which are not always practical).

    MongoDB should provide the ability to specify a "split" in a document such that the query planner can optimise disk access such that only the fields included by a projection are accessed.

    This would improve both write and read performance by allowing updates to subsets of the document to be targeted to specific disk regions. Likewise, queries which exclude large portions of the document can be optimised as they will no longer need to read potentially large sections of the disk.

    As an application's functionality grows, if kept unchecked it is easy for average document sizes to grow simultaneously.

    Large documents can have a significant impact on the performance of MongoDB. However, often the application doesn't actually need the entire document to service a request. Likewise, often queries are sent to MongoDB with a projection, excluding substantial (in terms of byte size) parts of the document.

    MongoDB has no ability to optimise these projections (except for covered queries which are not always practical).

    MongoDB should provide the ability to specify a "split" in a document such that the query planner can… 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  ·  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

11. Creation of Custom Views

    SQL based option to create view using multiple collections or databases

    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  ·  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. Make IAM database user authentication compatible with AWS SSO

    We are in the process of implementing AWS SSO across our Organisation and wanted to tie this in with mongodb-aws for database authentication.
    Unfortunately we have been informed the 2 services are not compatible.

    This would be a really useful add on to improve management of our systems.

    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

    3 comments  ·  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. Document known breaking change in JavaScript Engine

    If a new version of MongoDB will include a new version of MozJS (ex https://jira.mongodb.org/browse/SERVER-29286) and this version will break any existing scripts it would be ideal if this was documented.

    For example, with MongoDB 4.2 "value".contains() no longer worked in scripts and had to be converted to "value".includes()

    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  ·  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. Ability to create the resume token based on oplog item

    CHoose an oplog event to set the resume token for, instead of needing to run the change stream for system to create a resume token

    Why: Concerns about many stream re-reading a full oplog if failure before finding first event

    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  ·  Change Streams  ·  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. geoContain

    Dear all,
    according to the attached image, I have some documents (in blue, with id from 1 to 5) having a geographic extent and a search area (in yellow).
    I need to find all documents where search area is completly inside the document's geometry.
    Using different words, I need to find all documents where geometry completly covers the given search area.
    In my sample, the geo query should return the document with id 1.
    This kind of query has a opposite logic than the $geoWithin

    Could you provide a $geoContain functionality in the next future?

    •  

    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

    0 comments  ·  Query and Aggregation Pipeline  ·  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. view on nested array

    • It is quite common to have nested array in documents in MongoDB.
    • It is also quite common to have to "flatify" those arrays in queries.

    Here is an example where we have a collection with consultants and their professional experiences.

    consultant [{
       name:"Toto",
       age: 25,
       experiences: [{
          role: "Sofware Engineer",
          from: "2010-01-01",
          to: "2012-01-01",
          company: "CompanyA"
       }, {
          role: "Data Analyst",
          from: "2018-01-01",
          to: "2020-01-01",
          company: "CompanyB"
       }]
    }]
    

    If we would like to list all experiences at a company during a certain period of time, we would have to do an aggregate query with 3 steps that are sometimes error prone:
    - $match with $elemMatch
    - $unwind
    - same $match (without $elemMatch)

    "views" exists and make those queries much easier to create, with a simple find
    db.experiences.find({company:"CompanyA", from: {$gte: ... $lte...}})

    Unfortunately when using "views" the engine simply adds the match constraint at the end of the aggregation which turns out to be not always performant see https://support.mongodb.com/case/00767327.

    Would it be possible to create an option when creating a view that would be: Create a "view from nestedArray". It is quite simple to create an aggregation query where the query is better optimised because the match is done in the beginning.

        /** 1st match if elemMatch */
        stages.add(Aggregation.match(Criteria.where(nestedCollection).elemMatch(matchElemCriteria)));
        stages.add(Aggregation.unwind(nestedCollection));
        /** 2nd match without elemMatch */
        stages.add(Aggregation.match(matchCriteria));
        stages.add(new GenericAggregationOperation("$project", "{\"" + nestedCollection +"\": \"$" + nestedCollection + "\"}"));
        stages.add(new GenericAggregationOperation("$lookup", "{from: \"" + parentCollection + "\",\n" + "localField: \"_id\", foreignField: \"_id\", as: \"" + nestedCollection + "." + patientFieldName + "\"}"));
        stages.add(new GenericAggregationOperation("$unwind", "{ path : \"$"+ nestedCollection +"." + patientFieldName + "\"}"));
        stages.add(new GenericAggregationOperation("$replaceRoot", "{newRoot: \"$" + nestedCollection + "\"}"));
    

    • It is quite common to have nested array in documents in MongoDB.
    • It is also quite common to have to "flatify" those arrays in queries.

    Here is an example where we have a collection with consultants and their professional experiences.

    consultant [{
       name:"Toto",
       age: 25,
       experiences: [{
          role: "Sofware Engineer",
          from: "2010-01-01",
          to: "2012-01-01",
          company: "CompanyA"
       }, {
          role: "Data Analyst",
          from: "2018-01-01",
          to: "2020-01-01",
          company: "CompanyB"
       }]
    }]
    

    If we would like to list all experiences at a company during a certain period of time, we would have to do an aggregate query with 3 steps that are sometimes… more

    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  ·  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. VPC between ATLAS/MongoDB/AWS and Heroku/AWS

    Would be a great great feature if we can create a VPC between ATLAS/MongoDB/AWS and Heroku/AWS.
    Thanks.
    Adailton Silva

    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

    1 comment  ·  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. Cloning User/Roles along with Database

    When cloning a Database it would be helpful if User/Roles could be cloned directly as well and carried over.

    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  ·  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. Add option to repair a single collection

    Add support for repairing a single collection instead of what is currently available to repair an entire database via db.repairDatabase()

    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

    1 comment  ·  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. provide faster way to perform a count() on million documents

    a couple of customer a shifting from MongoDB to other DBs like Redis or even PostreSQL as count is too slow on MongoDB when there are a lot of document to count even with use of indexes

    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

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