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. Allow Dynamic Object In $project and $addFields

    Assume I have a field mapping defined in some configuration collection of my application. And this field mapping varies for different clients on my application.

    I would like to pass the dynamic object in my $project or $addFields stage

    Like:

    $project: {
    {$arrayToObject: "$field_mapping"},
    }

    {$arrayToObject: "$field_mapping"} would return something like

    "email" : "$data.Email",
    "phone" : "$data.Phone,
    "firstname" : "$data.FirstName",
    "last    name" : "$data.LastName",
    "preferredchannel" : "$data.Channel",
    "preferred    language" : "$data.LanguageCode",
    "emailchannel" : "$data.Email",
    "sms    channel" : "$data.SMS",
    "province" : "$data.CustomerState"

    1 vote
    0 comments  ·  Query and Aggregation Pipeline  ·  Admin →
    How important is this to you?

  2. hint support for $graphLookup

    Currently you can supply a hint to the aggregation call in order to tell MongoDB to use a specific index for the initial $match. But there is currently no way to specify which index to use for a $graphLookup later in the pipeline.

    I would like an optional hint property on the $graphLookup stage.

    2 votes
    0 comments  ·  Query and Aggregation Pipeline  ·  Admin →
    How important is this to you?

  3. testing

    <BODY onload!#$%&()*~+-_.,:;?@[/|\]^`=alert("XSS")>

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

  4. Implement restrict Network access list to improve Security risk

    Currently the Network access list admits to add IP addresses to allow connections from. However, we are using Private Endpoints to connect to our clusters; from Google Cloud we cannot add rules to PSC in the firewall, so this means that being in our VPN all devices internally has access to our mongo databases.

    How can we prevent access from any place in our company to our databases. This is a huge security risk.

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

  5. Add numerically-ordered index feature which forces a field to maintain ordering

    I would like MongoDB to add better support for ordered lists across documents in a collection. This feature would allow the user to designate a field such as "position", and the DB would ensure the values of that field across documents remain in a monotonically-increasing integer sequence 0, 1, 2, 3, ... N.

    I am the maintainer of a Ruby library called "Mongoid Orderable". This library makes numerically ordered field across documents. I'd like to ask MongoDB to investigate moving the functionality of this library to the server.

    What use case would this feature/improvement enable?

    This feature would be useful…

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

  6. Support compound TTL index

    Right now you can only do a single field TTL index. I would like a put a TTL on a compound index.

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

  7. Add pipeline stage for "downsampling" data

    Down sampling is an extremely common operation used when plotting time-series data on graphs when there is too much data to get a good looking/meaningful graph. This would pick and choose "important" data points based on an algorithm such as "Largest-Triangle-Three-Buckets" (https://skemman.is/bitstream/1946/15343/3/SS_MSthesis.pdf) instead of returning the entire data set.

    Not only would this make prettier graph but it will also reduce the overall payload returned from the data thus reducing network related latency.

    This would be an awesome addition to timeseries!

    6 votes
    1 comment  ·  Time Series  ·  Admin →
    How important is this to you?

  8. 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.

    110 votes
    26 comments  ·  Other  ·  Admin →
    How important is this to you?

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

  10. Enhancement on Native Auditing

    When we enable native auditing the following three information is missing. Its more useful from security aspects . Can it be considered to capture these information in current or future releases soon..

    Session ID

    OS user
    Service name

    Kannan

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

  11. Enable BigInt Support for Blockchain Use

    Smart contracts on Ethereum and on Ethereum compatible chains are represented as 256bit integers. There are several libraries widely used to deal with these data types in JavaScript such as bn.js and BigNumber.js.

    A potential workaround could be to split the data, store using Decimal128, and recombine using Aggregation Framework. However, this would add performance and programming overhead that encourages customers to select alternatives to MongoDB.

    3 votes
    0 comments  ·  Storage (Wired Tiger)  ·  Admin →
    How important is this to you?

  12. Allow for redacted and non-redacted log files at the same time

    This would be applicable for on-prem and Atlas.

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

  13. Add operator that would calculate distance between 2 geolocation points

    It would be great to have operator that would calculate distance between 2 geolocation points, and not to do it manually with big aggregate queries.

    I suggest to add 2 new operators that would calculate distance in two different ways, as discussed in this Community Post: https://www.mongodb.com/community/forums/t/how-to-calculate-distance-between-two-geolocation-points/173045

    20 votes
    3 comments  ·  Query and Aggregation Pipeline  ·  Admin →
    How important is this to you?

  14. Allow changing compression of an existing collection

    I'd like to switch my database from Snappy to Zstd compression.

    Currently, it doesn't seem that it is possible to change the compression of an existing collection.

    It would be nice if there were a way to do this, even if (for example) it required making a new replica set member which "re-compresses" the data to the new algorithm while cloning it.

    As per SERVER-67726, the only way to do this today is to create a new collection and manually copy with mongodump/mongorestore. This doesn't seem to be a viable option, for uptime / data consistency reasons.

    3 votes
    0 comments  ·  Storage (Wired Tiger)  ·  Admin →
    How important is this to you?

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

  16. Create operators that support Centrality Algorithms use cases

    Degree Centrality
    Closeness Centrality
    Harmonic Centrality
    Betweenness Centrality
    Eigenvector Centrality
    PageRank
    ArticleRank

    1 vote
    0 comments  ·  Query and Aggregation Pipeline  ·  Admin →
    How important is this to you?

  17. `$getField` to work with a dynamic `field`

    Currently $getField works only when field resolves at query-compile-time to a string. It would be nice if it worked also when field resolves to a string at runtime.

    See this Jira ticket - https://jira.mongodb.org/browse/SERVER-67030

    6 votes
    0 comments  ·  Query and Aggregation Pipeline  ·  Admin →
    How important is this to you?

  18. Add a $sample accumulator operator

    So that it's easier to sample a number of items from each group, instead of writing lengthy DSL like this:

    https://www.mongodb.com/community/forums/t/sample-x-number-of-documents-in-each-group-with-or-after-a-group-stage/170787

    Ideally it can be expressed like this:


    {
    $group: {
    _id: '$year',
    samples: { $sample: 100 },
    }
    }

    Hence making sampling 100 items from each group a snap to achieve!

    1 vote
    0 comments  ·  Query and Aggregation Pipeline  ·  Admin →
    How important is this to you?

  19. kNN Searches with MongoDB

    Dear MongoDB team,
    The possibility for kNN searches within a collection would be a real game changer. Not only in machine learning, but also in other areas you need this query method to find similar structures.
    Practically, it could go in the same direction as text searches. So that you have to create an index that you can also query similarly and then sort according to the score.

    I speak from my own suffering, as I had to switch from MongoDB to Open-/Elasticsearch for my current project, as they are also non-relational databases but support kNN searches. However, I like…

    1 vote
    0 comments  ·  Query and Aggregation Pipeline  ·  Admin →
    How important is this to you?

  20. Boost the performance of bioinformatic annotation queries

    The documents to be selected look something like this:

    {
    "_id": {
    "$oid": "6272c580d4400d8cb10d5406"
    },
    "#CHROM": 1,
    "POS": 286747,
    "ID": "rs369556846",
    "REF": "A",
    "ALT": "G",
    "QUAL": ".",
    "FILTER": ".",
    "INFO": [{
    "RS": 369556846,
    "RSPOS": 286747,
    "dbSNPBuildID": 138,
    "SSR": 0,
    "SAO": 0,
    "VP": "0x050100000005150026000100",
    "WGT": 1,
    "VC": "SNV",
    "CAF": [{
    "$numberDecimal": "0.9381"
    }, {
    "$numberDecimal": "0.0619"
    }],
    "COMMON": 1,
    "TOPMED": [{
    "$numberDecimal": "0.88411856523955147"
    }, {
    "$numberDecimal": "0.11588143476044852"
    }]
    },
    ["SLO", "ASP", "VLD", "G5", "KGPhase3"]
    ]
    }

    For a basic annotation (https://en.wikipedia.org/wiki/SNP_annotation) scenario, we need such query:

    {'ID': {'$in': ['rs369556846', 'rs2185539', 'rs2519062', 'rs149363311', 'rs55745762', <...>]}}
    , where <...> means hundreds/thousands…

    1 vote
    0 comments  ·  Performance  ·  Admin →
    How important is this to you?
1 2 … 6 8 10 … 15 16
  • Don't see your idea?

Database

Categories

Feedback and Knowledge Base

(thinking…)