Feedback

Showing 681 of 4027

The ciuster takes infinite time to get created. It has been in this state [We are deploying your changes: 3 of 3 servers complete (current action: waiting for restore to finish)] for over a day. Please help!

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. What would you like to see happen? Describe the desired outcome or enhancement. Why is this important to yo...

L Msaw about 11 hours ago in Performance & Optimization 0 Submitted

13 VOTE

Please add support for auto-incrementing numeric IDs. For example, if an ID starts at 1000001, the next created record should automatically use 1000002

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. MongoDB lacks native support for auto-incrementing numeric IDs, forcing applications to use custom counter logic, which in...

Altaab Ansari 2 months ago in Performance & Optimization / Querying & Aggregations 6 Future Consideration

149 VOTE

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

Guest over 3 years ago in Database 28 Submitted

8 VOTE

Provide safe canary deployment mechanism for index changes

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. 1. Unreliable index usage data 2. All-or-nothing risk with hideIndex() No ability to test on a subset of traffic or for a ...

surovskyi.y@ajax.systems surovskyi.y@ajax.systems 5 months ago in Data Modeling & Indexing 1 Will Not Implement

2 VOTE

Add Attribute Sorting/Reorganizing to get best index for $match in aggregation and other filters (by option)

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. I have found out that the order of attributes in my (different) $match stages are relevant to the query planner of what in...

Paul Coch about 1 month ago in Querying & Aggregations 0 Submitted

96 VOTE

Allow $search to be a later stage in the aggregation pipeline

Currently $search is required to be the first stage in the aggregation pipeline. It would be more intuitive if we could use after other operators, such as $match.

Guest almost 6 years ago in Atlas Search 9 Submitted

77 VOTE

Allow autocomplete search on multiple fields using a wildcard path or by specifying multiple fields in the path

Currently, (unlike the text operator) the autocomplete operator does not accept a path which is an array of field names. Also, a wildcard path ("path": {"wildcard": "*"}) cannot be specified for an autocomplete query. Therefore, the only way to pe...

Guest about 5 years ago in Atlas Search 10 Will Not Implement

6 VOTE

Improve small collection lookup performance

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. Improved performance for lookups from large to small collections (where many origin documents match the same looked-up doc...

Ryan Peggs 5 months ago in Querying & Aggregations 0 Future Consideration

76 VOTE

Dark theme

Uh, white background for people that work at night is ******* the eyes; better to have a dark theme.

Guest almost 6 years ago in Under Review 0 Submitted

13 VOTE

Support pagination when sorting by searchScore on Search Nodes

Using searchAfter / searchBefore on Search Nodes when sorting by searchScore can be inconsistent.

Guest about 1 year ago in Atlas Search 1 Shipped in Public Preview

Please enter your email address

FILTER BY CATEGORY