Feedback

Showing 116 of 4027

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

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

6 VOTE

`$getField` to work with a dynamic `field`

Currently `$getField` works only when `field` resolves at query-compile-time to a string. It would be nice if it worked also when `field` resolves to a string at *runtime*. See this Jira ticket - https://jira.mongodb.org/browse/SERVER-67030

Guest almost 4 years ago in Querying & Aggregations 0 Submitted

8 VOTE

function sandbox

It would be great to have a function sandbox area, where you can write and called previously used functions (saved like notepad++ does) without having to create the function and commit it. This would be for trying thing out or performing quick t...

Guest almost 6 years ago in Atlas Triggers and Functions 0 Submitted

3 VOTE

support parallel query executions include find(), aggregation()

To use multi-core environment and enhance the query performance w/ a large amount of documents, need a parallel execution. Sharding or microsharding is not an alternative in this case.

Guest over 2 years ago in Querying & Aggregations 0 Submitted

8 VOTE

Allow manually disabled trigger to resume without resume token

I am filing a feature request for the option to: Disable a trigger manually and be able to restart it without using a resume token (i.e. such that DB events that occurred while it was disabled will be ignored by the trigger, and it will simply sta...

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

3 VOTE

define the random seed manually, for $rand and $sample

It will be great if an additional paramater to define the seed for $rand and $sample could be use.

Guest over 2 years ago in Querying & Aggregations 1 Submitted

5 VOTE

Trigger event queue metrics

We recently ran into the problem that our trigger was suspended because the resume token was no longer present in the oplog. The problem was a combination of queued up trigger events and a short oplog window and the suggested solution was to incr...

Guest about 4 years ago in Atlas Triggers and Functions 0 Submitted

3 VOTE

$merge

Report number of docs matched, merged, skipped, etc. from a $merge stage. Alternatively, return the merged doc results as a pipeline result to pass to additional stages.

Charlie Little almost 3 years ago in Querying & Aggregations 0 Submitted

2 VOTE

Make $merge support DELETE operation

Currently, the `$merge` only supports insert/update/upsert/merge behaviour. It would be great to support delete behaviour. A common use case would be in-place document deduplication/clean-up in a collection.

Guest about 2 years ago in Querying & Aggregations 0 Submitted

Please enter your email address

FILTER BY CATEGORY