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

geo

It would be nice to get the length of an LineString of a geo-json object or the possibility to write an aggregation to calculate it.
Guest about 3 years ago in Querying & Aggregations 0 Submitted

Support concise correlated queries for $graphLookUp

Similar to $lookUp, support concise correlated queries for $graphLookUp. It would allow adding a $project stage to reduce overhead.
Guest over 1 year ago in Querying & Aggregations 0 Submitted

Ability to set Values in Functions

Ability from webhooks and functions to call context.values.set() and set a value that can then be referenced somewhere later. This could dramatically cut back on calls to outside APIs as we need data in multiple places so we end up having to make ...
Guest almost 8 years ago in Atlas Triggers and Functions 0 Submitted

Support Multiple CRON Schedules Per Trigger

It's not uncommon to want different trigger schedules to run on different days of the week, notably weekdays and weekends. The current solution is to create separate triggers that call the same function, but ideally, a single trigger could support...
Guest about 3 years ago in Atlas Triggers and Functions 1 Submitted

Add hash function (eg. md5) to aggregation pipeline

I would like to implement hash-based sharding in my own application on top of MongoDB. For that purpose, I would like to pull a stable pseudorandom subset of documents into each of my servers, and I would like to do so without enlarging the docume...
Guest about 3 years ago in Querying & Aggregations 0 Submitted

Triggers on DB level rather than single collections only

Change streams support events on DB level *or* single collections, but triggers are limited to single collections. Which means that if we wanted to listen on changes in a generic way, we would have to setup a trigger for each collection and set th...
Guest about 3 years ago in Atlas Triggers and Functions 0 Planned

$dateDiff operator should be useful to calculate age

In the documentation it says: " For example, two dates that are 18 months apart would return 1 year difference instead of 1.5 years.". But if startDate is 2021-08-01 and endDate is 2023-02-01, the result is 2 years difference. I think it should be...
Guest about 3 years ago in Querying & Aggregations 1 Submitted

Meaningful errors

Descriptive errors are crucial for debugging and simply cannot be found with Atlas App Services ! 1) If an error occurs - the whole function cascade is terminated - not only the steps following the error but also the ones prior to it. i.e. if a co...
Guest over 3 years ago in Atlas Triggers and Functions 0 Submitted

Call Functions In Background

Currently, if you call a function for example function_1 from a separate function function_2. Function_2 will wait for function_1 to execute and return before continuing. We have a function that we'd like to use to execute a different function wit...
Guest over 1 year ago in Atlas Triggers and Functions 0 Submitted

$sort should allow 0 as argument meaning "no sort"

The $sort operator and aggregation stage should allow 0 (possibly also null) as an argument for the field sort order, meaning, "Don't sort." This allows a variable to be passed in that can conditionally skip the sort operation, in addition to the ...
Guest over 1 year ago in Querying & Aggregations 0 Submitted