Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

Feedback

Showing 415 of 4027

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 detai...
Guest almost 4 years ago in Database 0 Submitted

Lock on session start level with provided keys

Scenario: Parallel DB updates with transactions on multiple collections that use same documents. Example: Calculate some common stuff to embed it in extra collections to avoid lookups. Problem: Lock and timeout on documents uses up valuable time ...
Guest over 2 years ago in Storage & Transactions 0 Submitted

Validation should support default values

Various users feel that validation should support default values. See, for instance: https://www.mongodb.com/community/forums/t/support-default-value-in-schema-validation/319684 https://www.mongodb.com/community/forums/t/setting-default-values-in-...
Guest 12 months ago in Data Modeling & Indexing 0 Submitted

Allow kill connections

Kill session commands only stop current activities on DB, but not closing/dropping connections (connections still remain open in $listSessions). It´d be useful to be able to close opened connections in situations where too many sessions have been ...
Guest almost 6 years ago in Database 0 Submitted

Allow the ability when NVME cluster to autoscale up based on CPU and Memory

To provide autoscaling capability for MongoDB NVME clusters based on CPU utilization and memory metrics. This feature would automatically provision additional resources when predefined thresholds are reached, ensuring optimal performance during us...
Guest about 1 year ago in Performance & Optimization 0 Submitted

Raise the limit of 16 MB JSON between aggregation stages

When doing analytics, the 16 MB JSON limit between aggregation stages restricts the ability to process large amount of data. allowDiskUse does not help with all the various $operators and stages that we use. See ticket 00774514 for details.
Guest about 4 years ago in Querying & Aggregations 0 Submitted

Introduce int8 (and int16) data types

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. Having int32 as the smallest integer type means even values which can't go over 127 (as is common with enums) have to take...
Er Fr 5 months ago in Database 0 Future Consideration

Handle Daylight Saving Time when $densify is used on a date field

When using "day" as "unit" for a $densify pipeline stage on a date field, the date is always advanced of 24 hours. This is however not always the expected result in timezones in which the year has one 23-hour and one 25-hour long day, because of D...
Guest over 3 years ago in Querying & Aggregations 1 Submitted

Disallow new connections that don't specify an appName field

Currently as a DBA it's sometimes hard to identify which service is causing load on a shared cluster/database. Some people connect for adhoc workloads but don't specify an appName making it hard to track back to the owner. It would be useful to re...
Guest about 1 year ago in Database 0 Submitted

Ability to set maxClauseCount for cli image

We have a query that needs to filter by a long list of ids. I get the error: “Query contains too many nested clauses; maxClauseCount is set to 1024” This error does not happen in M10+ cluster because the lucene maxClauseCount seems to be higher ...
Guest over 1 year ago in Atlas CLI 1 Submitted