Feedback

Showing 234 of 4027

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

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

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

5 VOTE

Add Dedicated Search Nodes to more regions in Europe (eu-west-3)

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. We want to use Dedicated Search Nodes. Our regions are eu-central-1 and eu-west-3. Dedicated Search Nodes are only availab...

Jose Molero 5 months ago in Atlas Search 1 Future Consideration

68 VOTE

Please support on-prem installations

Can we get Search on-prem? Is this always going to be an Atlas-only feature?

Guest over 6 years ago in Atlas Search 27 Started

10 VOTE

Sorting within nested objects. Allow filters on sort operation

Atlas search sorting currently only supports a direct sort on root level fields or nested fields indexed as type "document": https://www.mongodb.com/docs/atlas/atlas-search/sort/ Sorting cannot be done in conjunction with a filter, so a sort oper...

Guest about 1 year ago in Atlas Search 1 Submitted

16 VOTE

Support Collation for Atlas search sort

I have a use case to sort by product names (strings). We have products that start with letters and some that start with numbers. Currently, the products that begin with numbers are always at the top when you sort in ascending order. We would like ...

Tom Richter almost 2 years ago in Atlas Search 1 Submitted

Please enter your email address

FILTER BY CATEGORY