Skip to content

Database

← MongoDB Feedback Engine
To report bugs, please use our SERVER JIRA project.

How can we improve the MongoDB Database?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

314 results found

  1. views on different database (synonyms)

    It would be great if we could have in Mongo the same as in Oracle with DBLink synonyms:
    Access table or views from a different database.

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

  2. add view，index，user，role to mongodb Change Stream

    I tested the changeStream of mongodb. The changes of adding view, index, user and role to mongodb are not reflected in changeStream, but the corresponding log can be found in oplog. I have an issue on https://jira.mongodb.org/browse/SERVER-66460 and got it confirmed, but Chris Kelly thinks this should be a feature. Hopes to add this feature in future versions

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

  3. Support readOnly in Json Schema Validation

    Support the readOnly property for json schema validation to make certain fields immutable (or the entire document) after creation.

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

  4. STIG for MongoDB 6

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

  5. STIG for MongoDB 5

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

  6. 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…

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

  7. Support expressions in $densify range bounds

    The $densify aggregation pipeline stage seems unable to evaluate range bounds expressions, requiring the range bounds to be constant.

    See the following example (the collection testcoll contains a single documents with only the _id field):

    sometestdb> db.testcoll.aggregate([{$addFields: {a: 1}}, {$densify: {field: "a", range: {bounds: [0, 5], step: 1}}}])

[

  { a: 0 },

  { _id: ObjectId("6284a16d64553eaf74b1e189"), a: 1 },

  { a: 2 },

  { a: 3 },

  { a: 4 }

]



sometestdb> db.testcoll.aggregate([{$addFields: {a: 1}}, {$densify: {field: "a", range: {bounds: [{$toInt: "0"}, 5], step: 1}}}])

MongoServerError: A bounding array must be an ascending array of either two dates or
    …
    3 votes
    3 comments  ·  Query and Aggregation Pipeline  ·  Admin →
    How important is this to you?

  8. Use dedicated interface for replication and balancing

    Like many other big database system, MongoDB may support to specify dedicated interfaces for replication and/or for the balancer (sharding)

    Currently you can configure replication sets and shards members only by single hostname/IP-Address, i.e. all data is transmitted over the same network interface.

    2 votes
    0 comments  ·  Replication  ·  Admin →
    How important is this to you?

  9. Change how document size is calculated

    Disclaimer: I'm aware that this is a pretty big feature request.

    Currently a document has a max size of 16 mb. I'm not suggesting changing that. However, I'm suggesting changing how that size is calculated.

    I'm designing a database in which documents have a tree structure. The document will have an array called "nodes", which can hold any number of child nodes. Those nodes can also have arrays of nodes, and so on. It's a simple tree structure.

    For major users of my application, that outer document could get pretty big. It's not a problem right now (no users, no…

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

  10. Make it possible to delete a database via API

    It would be nice to be able to delete a database in a replica set via an API call. This would make it easier for CI/CD when deleting clients
    Strange thing is that I can delete a complete cluster, but more fine-grained deletion is not possible. like deleting a replica set or only 1 database in a replica set. The most dangerous one is available via API :)

    13 votes
    1 comment  ·  Versioned API  ·  Admin →
    How important is this to you?

  11. Make it clear an index not on present on all shards

    We recently had an issue where an index did not get created on all shards. When we ran getIndexes() on mongos it reported the index was present. So we dropped another redundant index thinking all would be well - it was not. We had serious performance issues on the shard that was missing the new index and our app was unavailable for a few hours whilst we re-created the missing index on a huge collection.

    It would be better if getIndexes called on mongos reported some sort of warning or indication that it was not present on all shards. The…

    2 votes
    0 comments  ·  Indexes  ·  Admin →
    How important is this to you?

  12. Get metadata about source client connection that submitted a given change

    Currently with change streams it is impossible to know who or what connection initiated the changes.

    It would be a good feature to have to be able to receive some data about the source client connection that initiated a change.

    My particular use case is the following:

    I have an app that connects to Atlas. (source client connection)
    I can subscribe to change streams and then execute some logic when it applies.

    That app can scale to multiple instances.
    Each instance subscribes to the change streams.
    But I only want each instance to execute the logic that applies to only…

    5 votes
    0 comments  ·  Change Streams  ·  Admin →
    How important is this to you?

  13. Enforced Password Complexity

    Please allow for the enforcement of password complexity:
    - Setting a password policy that restricts users to a certain level of complexity (e.g 10 chars with special characters)

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

  14. collection-level users should be able to list their collections

    Currently users with collection-specific read or read/write permissions are not authorized to perform the following commands:

    db.listCollections()
    show collections
    db.getCollectionNames()

    This impacts the shell (and also third party tools that won't let users access their permitted collections because the list of collections is blocked in the first place)

    Suggestion:

    Users with collection-specific read or read/write permissions should be able to run the above commands and the result would only present the collections for which the user has some read or write privileges (instead of blocking everything).

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

  15. Multi-version-intermediate upgrade package

    When upgrading the MongoDB server community edition from a very old version to the newest version one cannot skip installing intermediate versions, e. g. version 3.6 -> 4.4 does not work because the database files cannot be auto-migrated and the FeatureCompatibilityVersion is too low on 3.6 (or not existent).

    Instead we have to install 3.6 -> 4.0 -> 4.2 -> 4.4 and execute db.adminCommand( { setFeatureCompatibilityVersion: "..." } ) appropriately in between installing each new version.

    I propose creating an additional installer package for Linux which takes care of all that to migrate the internal database structure from the installed…

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

  16. Add SSO authentication support to mongoDB database

    Existing issue: One user has accounts in multiple mongoDB databases on Atlas that exist in different Projects and maybe Organizations as well. When he wants to switch from one database to the other from a 3rd party app, he has to provide his credentials every time.

    Adding SSO authentication support to the mongoDB databases would add flexibility to a user like that, to switch from one database to the other without being asked for his credentials every time when connecting from a 3rd party application.

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

  17. Have an API to have the History of Primary Nodes

    Have an API to have the History of Primary Nodes,from the time the Replica set is initiated.I know we can have alerts for Primary switch over,but if we want to analyse the data of elections/primary node for say about last 1 year , an API would help.

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

  18. CSFLE - Enable aggregation stages for non-encrypted collections

    When encrypting any collection with CSFLE, aggregation is not allowed on non-encrypted collections.

    The official recommendation is to maintain 2 clients: 1 for CSFLE and 1 for when aggregation is needed. How is this an acceptable solution?

    2 votes
    0 comments  ·  Encryption  ·  Admin →
    How important is this to you?

  19. 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
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  20. Support mongos + ops manager agents as a container sidecar

    1 vote
    0 comments  ·  Workload Management  ·  Admin →
    How important is this to you?
1 2 … 7 9 11 … 15 16
  • Don't see your idea?

Database

Categories

Feedback and Knowledge Base

(thinking…)