Feedback

Showing 415 of 4027

Bidirectional Data Replication beetween two or more clusters

In order to provide active-active deployments on multiple datacenter without need to shard data and route trafic based on shard-key. Develop a bidirectional replication with a conflict resolution method , for example , timestamp-based.

Guest over 4 years ago in Replication & Sharding 0 Submitted

1 VOTE

Features missing in Mongodb MCP server

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. Current MongoDB MCP server support is very limited for certain operations. Developers are constrained to a narrow set of t...

Shailaja Gummudhavelly 3 months ago in Atlas CLI 0 Will Not Implement

3 VOTE

Native Support for Date-Only and Time-Only Field Types

### Summary MongoDB currently lacks native field types for **date-only** (e.g., `2025-05-28`) and **time-only** (e.g., `13:45:00`) values. This results in frequent developer confusion, incorrect behavior around time zones, wasted storage, and the...

Guest 8 months ago in Data Modeling & Indexing 0 Submitted

1 VOTE

Add setOnUpdate operator for Upsert operations

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. We regularly want to upsert documents to mongo, and include a useful createdAt and updatedAt timestamp. createdAt is easy:...

WelcomeLend Operations 3 months ago in Querying & Aggregations 1 Future Consideration

2 VOTE

Per-Shard Change Stream and Triggers to improve scalable/performance/resilience

In our geo-sharded cluster, we use Change Streams and Atlas Triggers. Most of our pipelines include a 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 streams wit...

Boris Figovsky 7 months ago in Database / Replication & Sharding 1 Submitted

12 VOTE

Nanosecond timestamp support

I've put this under the time series category since that's where it's most applicable, but it's really a data model / BSON issue. The topic of higher resolution timestamps have been surfaced from time to time for at least a decade (https://jira.mo...

Guest over 3 years ago in Database 1 Submitted

14 VOTE

Make it possible to delete a database via API

It would be nice to be able to delete a database in a replica set via an API call. This would make it easier for CI/CD when deleting clients Strange thing is that I can delete a complete cluster, but more fine-grained deletion is not possible. lik...

Guest almost 4 years ago in Database 1 Submitted

9 VOTE

Should be possible to configure profiling output destination

When enabling database profiling the output is sent to both the system.profile collection and system logs. Logging to a capped collection is fine but spamming the logs on disk is not good. We have a need to be able to react to changing query patt...

Guest over 2 years ago in Performance & Optimization 0 Submitted

1 VOTE

MongoDB missing support for GeoJSON-compliant indexing+intersection queries

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. We are building a geospatial application that uses GeoJSON natively. We need to query MongoDB for a list of GeoJSON object...

Mitchell Horning 4 months ago in Querying & Aggregations 0 Future Consideration

16 VOTE

Higher IOPS for small disk sizes (MongoDB Atlas on Azure)

AWS and GCP start with 2300-3000 IOPS for M10+ instance from the smallest disk size (8Gb), whereas on Azure we get 120 IOPS with 8Gb, 240 with 64Gb, 500 IOPS with 128Gb ... nowhere near to what AWS/GCP offer (120 - 500 IOPS for a database server i...

Guest over 4 years ago in Database 2 Submitted

Please enter your email address

FILTER BY CATEGORY