Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

Database

Showing 316 of 4026

Implement a $hash operator for queries

Current State: MongoDB currently lacks a native $hash operator in the aggregation/query language. While certain helpers like convertShardKeyToHashed or $toHashedIndexKey exist, they are limited in scope: Not available as true query operators (e....
Guest 9 months ago in Querying & Aggregations 0 Submitted

Work towards making Mongo usable for Non tech users/founders/CEO with AI

What problem are you trying to solve? Focus on the what and why of the need you have, not how you'd like it solved. Example: Data management and CRM. What would you like to see happen? Describe the desired outcome or enhancement:The experience cou...
CREWBELLA Ecosystem 2 months ago in Data Modeling & Indexing 2 Future Consideration

Password enforcement without LDAP

Enforce complex password policy Enforce password expiration Enforce password history
Guest almost 6 years ago in Database 6 Submitted

Unique Indexes and Bulk Upserts for Time Series Collections

We would like to insert data in bulk into time series collections and identify the new data that has been inserted without the possibility of duplicates being inserted. For regular collections this is achievable by adding a unique index and perfo...
Guest about 3 years ago in Database 0 Submitted

Cloud collaboration for Data modelling

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. Teams cannot effectively collaborate on data models and visualizations in MongoDB Atlas. These artifacts are currently use...
Michael Tijhuis 2 months ago in Compass & Data Explorer / Data Modeling & Indexing 0 Future Consideration

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

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

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

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

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