Feedback

Field Mappings in webui should show updatedAt

https://cloud.mongodb.com/v2/id#/clusters/atlasSearch/name?database=db&collectionName=col&indexName=default&view=IndexOverview Field mappings please show when the field mappings were last updated

Guest 6 months ago in Atlas Search 0 Submitted

1 VOTE

Per-Shard Triggers to improve scalable/performance/resilience

In our geo-sharded cluster, we use Change Streams and Atlas Triggers. Most of our pipelines include an exact match for the shard key - so we can process the data in the same region where the data resides. However, due to the design of change str...

Boris Figovsky 7 months ago in Atlas Triggers and Functions 0 Submitted

12 VOTE

Support for arrayFilters in Functions

Can we add arrayFilters and other array update capabilities that already exist in MQL? Its is difficult to update arrays, and very easy to update an array in MQL in node.js for example.

Guest over 6 years ago in Atlas Triggers and Functions 3 Planned

7 VOTE

Allow to pass user on Realm's Database Triggers

Currently I can create a Database Trigger, that when calling its Function I can restrict based on "%%user" - through "Can Evaluate". Though since the Function is called by a Trigger and therefore runs as a "system user" I cannot access the User ob...

Guest almost 4 years ago in Atlas Triggers and Functions 2 Submitted

7 VOTE

Support min-max computation for number and date fields, within Atlas Search

Currently, the `$min` and `$max` aggregation operators can be used in a number of aggregation pipeline stages, in order to find min/max values for fields. It would be great if either these operators were supported within `$search`, or if there was...

Guest about 4 years ago in Atlas Search 0 Submitted

3 VOTE

Ability to choose what to dynamically index

When using dynamic mapping, it would be useful for better control on the index to allow choosing which index types are created. Exemple: dynamic: true // Map all fields dynamic: false // Don't use dynamic mapping dynamic: ["string","bool"] // O...

Guest almost 2 years ago in Atlas Search 0 Submitted

1 VOTE

Add noData to $sort aggregation

Atlas Search does have the option to change the behavior for null and missing values within a search with noData: highest or noData: lowest. It would be great if the $sort aggregation stage would support this as well.

Guest 7 months ago in Atlas Search 0 Submitted

6 VOTE

Support full Lucene Query Parser syntax in $search

I’m looking to expose “power user” queries through our UI, but the queryString operator only works on string data types, and is somewhat too simplistic for this purpose. Obviously, accepting raw user inputs and directly building a query from it i...

Guest over 3 years ago in Atlas Search 1 Submitted

7 VOTE

Realm Trigger Event Projection should support exclusion

Realm triggers with a projections must include "operationType": 1. This makes excluding fields impossible because, according to the documentation: if you exclude fields, you cannot also specify the inclusion of fields The only work around we hav...

Guest over 4 years ago in Atlas Triggers and Functions 2 Submitted

5 VOTE

Grouping in $search

Add grouping capability to search so that it can be as performant as the search itself. A separate group stage is not performant at all and is unusable.

Guest about 3 years ago in Atlas Search 1 Submitted

Please enter your email address

FILTER BY CATEGORY