7 results found
It would be nice to be able to managed Realm Applications via Terraform, similar to how MongoDB Atlas can currently be managed via the mongodb_atlas from Terraform provider.13 votes
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.11 votes
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 start listening for new events upon restart).8 votes
Currently deployent is only available to AWS but Atlas allows deployment in GCP.
We need to have deployment close to GCP for better performance consideration.7 votes
The maximum return body size of a realm webhook is 4MiB (4194304 bytes). That might seem enough for most applications but when dealing with massive amounts of data, e.g. timeseries data over years, that is a hard limitation.
It requires the client to make many more requests that would be necessary.
In our special case we want to return one whole year worth of data per request to make things easier for our clients (currently they can get 3 months).
Given a 16MB Limit on a MongoDB Collection Document, this would seem like a sensable option for a limit if…5 votes
Hi Marc – We have a ticket for this that’s near the top of the backlog and plan to increase the limit to 16MB in the near future.
We are in the process of migrating from a hand-implemented Apollo server to Mongo Realm, but are finding the inability to reuse types on custom resolvers to be a serious impediment.
For example, we have a number of custom resolvers that use the same type to define a temporal interval, but we cannot reuse that type in the arguments for our custom resolvers as Stitch will throw an error upon encountering those duplicated types. Additionally, many of these custom resolvers return the exact same type, but if we try to reuse that same type definition Stitch will throw errors about…5 votes
Hi Folks – This improvement is already planned and should be completed shortly.
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 them up with AWS EventBridge (and think about new triggers when new collections are generated).
Given that the underlying tech (change streams) supports DB-level subscriptions, we would really like to see that on the UI, too.2 votes
- Don't see your idea?