Skip to content

Database

To report bugs, please use our SERVER JIRA project.

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

272 results found

  1. Pass document field to $loolup.from and $lookup.as

    Suppose I have collection of documents { entityId, entity }, where entity is names of other collections I would like to make aggregation with lookup and be able to pass entity value to $lookup from and as

    db.collection.aggregation([{ $lookup: { from: '$entity', let: { entityId: '$entityId' }, pipeline: [{ $match: { $expr: { $eq: ['$_id', '$$entityId'] } } }], as: '$entity' } }])

    As of mongo v4.4.4 that seems not working.

    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. Have a role that allows that user to control the schema of a collection

    As a DBA or Data Architect, I want to be able to enforce data governance policies like schema control. Users of MongoDB cannot change the schema however DBA or named individuals have the ability to change the schema.

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

    geoIntersect queries on spherical geometries are not adapted to our use case. Our need is to retrieve a list of tiles intersecting a given area of interest (AOI) in a flat 2d geometry.

    Classical geo-spatial databases (PostGIS and Oracle Spatial) support this kind of approach at no extra cost and we would expect the same from MongoDB.

    In MongoDB , using a 2dsphere index forces us to implement a workaround adding an artificial margin to the AOI and making a post-processing to remove false positives. See attached slides for explanations.

    Best Regards

    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. Support for Ubuntu 20.4 in MongoDB Server version 4.2

    Per the Server Support Matrix https://docs.mongodb.com/manual/installation/ support for Ubuntu 20 is in MongoDB Server version 4.4+ but not 4.2.
    We would like to see the currently supported MongoDB Server version 4.2 available on the Ubuntu 20.4 LTS distribution.

    5 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)
  5. log connection string used by application to connect

    there are multiple options to connect to mongo: you can connect to specific node or you can connect to the whole replicaset etc...
    if DBA does not have access to source code - it's not possible to validate if application properly configured and connects to replicaset.

    it would be nice to let mongoDB dump to mongod.log used connection string and/or details how exactly client sessions is connected to mongo.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Low latency Change Stream for Global Cluster in Atlas

    our event-driven applications need to publish events to Kafka triggered by Change Stream feature. It works perfect in replicaset MongoDB cluster.

    However, after migrating to Global Cluster in Atlas, the Change Stream cannot keep low latency because of ordering reason among shards.
    The latency may go up to 20 seconds when for a single change event.

    It would be nice if application can receive Change Stream from the single shard only (not care about ordering among shards) to prevent latency.

    The idea is to pass "location" options when starting the Change Stream cursor.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Diacritic insensitive contains search on a single field

    I would like to perform a "contains" query on a single text field in a case insensitive and diacritic insensitive way. I would like the query to have the performance of the field being in a text index by itself (assuming that this gives the maximum speed).

    It is usually the case that the text index already exists for multiple fields. This means that a text search then has to be combined with a complicated (to make it diacritic insensitive) regex expression to find the correct results.

    https://developer.mongodb.com/community/forums/t/query-for-field-containing-a-string-case-in-sensitive-and-diacritic-in-sensitive/14814/2/

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

    When porting an application backend from an RDBMS to MongoDB, we've spoken to two people who've are looking for a way to specify a limit on the number of documents in .updateMany(). I understand the behavior cannot be defined on a sharded cluster, but if we had a way to do this on an unsharded collection, that would help when dealing with these teams.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add an option for $addToSet to use a specific field in the array for uniqueness

    Currently, the $addToSet for upserting to an array checks for object equality (when the array elements are objects). We sometimes need to check for uniqueness based on a specific field of the object rather than the object as a whole, and the only way to do this is to force single-threaded operation and to use $pull and $push.

    If there is a way to specify the field to check uniqueness for the $addToSet , we would be able to perform writes normally.

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

    Add support for Extended JSON (EJSON. For example, {$date: "2021-01-01T00:00:00.000Z"} ) such that we do not have to resort to using the ISODate helper function in the MongoDB Shell and in Compass.

    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. Arrow function support

    Is there any plan to implement arrow functions support?
    The current way to use functions (BSON type 13) is using traditional javascript functions:

    function() {
    ...
    emit(key, value);
    }

    It would be great to support also arrow functions:

    () => {
    ...
    emit(key, value);
    }

    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)
  12. options for different compute configuration per shards

    Can we have options for different compute configuration per shards?

    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)
  13. Aggregate $accumulator 'Combine' stage for sharded collections

    After the ‘accumulate’ stage has run against each document on a shard it would be extremely useful to run a script on the shard against the state to reduce the state down to something smaller before passing the final state over the network back to mongos for the ‘merge’. (Over in the Elastic camp they call this the ‘combine_script’).

    Scenario:
    I have a customer orders database sharded by the Customer ID (meaning all data relating to any specific customer is kept on the same shard - so customers don’t need to be ‘merged’ between shards). I can write an accumulator…

    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)
  14. 4.4 to the EU on regular instance for development!

    I work on mongodb in the EU.. i want to use the atlas search but i also need some features of v4.4

    In development and for general everyday projects where our clients don't have large user bases we generally go for M2 instances.. affordable while offering full text search.

    The release of 4.4 is almost half a year old.. when will we see 4.4 released to the EU of regular M2 instances??

    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. Option to prohibit a non-voting member from becoming a sync source of a voting member

    Hi,

    Our proposition in a few words: add a replica set option to allow chained replication but with the following exception: a non-voting member cannot become a sync source of a voting member under any circumstance.

    This proposition would allow chained replication for clusters having both w=majority writes and analytics nodes.

    Right now, those clusters cannot safely enable chained replication, because under some circumstances, the non-voting analytics member may become the first secondary in a serial chain of replication. In that case, this node[*] slows down the replication process for all downstream secondaries. Higher replication lag translates to extremely slow…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Bundle rest service together DB

    As per current industry practice, REST/Json became standard way to deal with the data between the FE application and Backend DB. So if REST the server/service is bundled with DB it would eliminate the need of a middleware tier in most cases.

    It means we can directly fetch data from a frontend application using REST/Json from mongoDB without requiring a thirdparty service.

    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)
  17. EDGE

    Localisation

    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)
  18. Assign MongoDB roles to LDAP users

    I would like to create a softlab and therefore give the possibility to a user to create collections in a database which is dedicated to him.

    Currently, to do that I need to :
    1. create a single-member LDAP group for each user
    2. map this group to a MongoDB role authorizing the user's database.

    Create a group with a single member is conceptually useless. I want to avoid step 1.

    My feature request : add the ability to assign MongoDB roles to LDAP users as well as groups.

    Regards,
    Jerome

    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)
  19. Allow custom autoscaling policies

    Currently this is the following autoscaling policy in mongo:

    Please note, if the next highest cluster tier is within your Maximum Cluster Size range, Atlas scales the cluster up to the next tier if one of the following is true for any node in the cluster:

    Average CPU Utilization has exceeded 75% for the past hour, or
    Memory Utilization has exceeded 75% for the past hour.

    The feature request is to allow a DBA to setup custom autoscaling policy

    8 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)
  20. Conditional TTL index

    In case of auto purging sometimes user might want to ensure data has been archived before purging. If conditional TTL was allowed user could set value of a field to indicate document has been archived and then db can purge accordingly.

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

Feedback and Knowledge Base