Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
9 results found
-
Add support for allowDiskUse when using the Data API
The Data API doesn't support the allowDiskUse option, leaving no way to get around this error:
"Failed to aggregate documents: FunctionError: (QueryExceededMemoryLimitNoDiskUseAllowed) Exceeded memory limit for $group, but didn't allow external spilling; pass allowDiskUse:true to opt in"
9 votes -
Allow API Access via Private Endpoint Connection
To automate processes ATLAS Admin API is used but does only work if your cluster is not connected via Private Endpoint.
4 votes -
WriteOnly DATA API
Hello,
We have a similar need as the one in ticket 44935186, but we would like a WriteOnly (no delete nor read) access to the API so a partner could push data in a collection without being able to read it
Thx and have a nice day!
3 votes -
REST API for sizing and pricing information
To keep our configuration on optimized terms we need a way to keep sizing and pricing data of the configuration on our side up to date. We have to get this information automatically for example via REST API.
This would help us to be up to date concerning
- Tier sizing: e.g. tier, RAM, CPU, min HDD, price included HDD, max HDD
- Pricinig: e.g. how much $ per hour / month for tier ***, with XX GB HDD and RAM, KMS encryption, backup and so on3 votes -
API KEY - Restrict by Database
Since Mongodb Clients cannot be used in Edge Runtimes (like Vercel, Cloudflare, etc.) the user of Data API becomes inevitable. The Data API access should have same features like user roles where we can restrict an API KEY or an ENDPOINT to have acccess to a single database or multiple database.
2 votes -
Handle Duplicate data in Timeseries collection
It would be helpful by introducing the optional add on functionality of overwriting the document if it is already exists for an insert operation based on “_id” field for only timeseries collection in upcoming releases. Because if we have huge amount of sensors then data should be blindly written into timeseries collection without querying for duplicate check (Conditional inserts will definitely impact the performance).
1 vote -
grpc
You should create a grpc API like AstraDB has already done. Grpc is the ideal way for a serverless app to connect to a database. Get both of best worlds: native driver performance plus don't need to worry about database connections.
1 vote -
Disable (or warn about) destructive features
We already have Termination Protection enabled in our production cluster. That's great, but only applies to the whole cluster.
It would be great if there was a way to enable additional finer-grained safety features in MongoDB that would apply to large-scale destructive actions taken in either Atlas or mongosh. These could be presented as additional warnings or require additional confirmation even for users with administrator rights to re-consider their life choices. I.e. "are you really REALLY sure you want to drop that collection?". These could apply to the entire project, rather than individual databases or collections.
For example, these features…
1 vote -
Add C# Android app support
The C# driver wraps the DnsClient library. This does not support Android so I can't access an Atlas server from a Xamarin mobile ap on Android. Perhaps you could either use another library or create a bespoke library which includes Android DNS lookup support?
1 vote
- Don't see your idea?