Feedback

Add line number to function call error messages

A simple line number of where a function fails would be incredibly useful. And a function name would be important too for when a function calls another function.

Guest over 5 years ago in Atlas Triggers and Functions 3 Submitted

4 VOTE

Project out embedding fields by default in $vectorSearch

We should update the default behavior to project out embeddings, since they are typically not used in subsequent aggregation stages, with an additional query parameter to force include them.

Guest almost 2 years ago in Vector 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

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

2 VOTE

Binary and Scalar Quantization

These capabilities will reduce vector sizes while preserving performance, enabling developers to build powerful semantic search and generative AI applications with more scale—and at a lower cost.

Guest over 1 year ago in Vector Search 0 Submitted

1 VOTE

vector search index switch

Since the vector name must be explicitly specified when running a query, it is difficult to update the vector without causing downtime or making code changes. It would be useful to have an option in Atlas to switch between two indexes , or to rena...

Guest 9 months ago in Vector Search 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

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

Please enter your email address

FILTER BY CATEGORY