Add support for Extended JSON (EJSON. For example, {$date: "2021-01-01T00:00:00.000Z"} ) such that we do not have to resort to using the ISODate helper function in the MongoDB Shell and in Compass.

Is there any plan to implement arrow functions support?
The current way to use functions (BSON type 13) is using traditional javascript functions:

function() {
...
emit(key, value);
}


It would be great to support also arrow functions:

() => {
...
emit(key, value);
}


Can we have options for different compute configuration per shards?

I work on mongodb in the EU.. i want to use the atlas search but i also need some features of v4.4

In development and for general everyday projects where our clients don't have large user bases we generally go for M2 instances.. affordable while offering full text search.

The release of 4.4 is almost half a year old.. when will we see 4.4 released to the EU of regular M2 instances??

As per current industry practice, REST/Json became standard way to deal with the data between the FE application and Backend DB. So if REST the server/service is bundled with DB it would eliminate the need of a middleware tier in most cases.

It means we can directly fetch data from a frontend application using REST/Json from mongoDB without requiring a thirdparty service.

Localisation

In case of auto purging sometimes user might want to ensure data has been archived before purging. If conditional TTL was allowed user could set value of a field to indicate document has been archived and then db can purge accordingly.

collections under a document as in firebase firestore

This request is for a tuneable parameter to allow the number of parallel chunk migrations to be limited.

TTL expiration on an embedded subdoc will delete the parent/root doc.

Provide an option to only delete the subdocument on expiration.

Collation of a collection can be set at creation time only. It would be useful to edit these fields to avoid creating an entire new collection and copying the collection over.

Currently, with the JSON Schema validation, we are able to limit the values for a field using enumerations. However, we need to have a way to limit the values to those entered in another collection.

We have multiple microservices using the same collection and we'd like to track how many calls come from each, and also understand which transactions are successful or not.
Ultimately this will allow us to understand the MDB usage by each of the microservices.
[setting verbose logging level to 1 and then using these logs to create a dashboard in Splunk doesn't give us enough granularity]

I would like to be able to find all geoJSON points located within a collection of polygons. My personal goal is to find points located within earth's water bodies. The water bodies are located in their own collection while the geoJSON points are located in a separate collection within the same DB. Mongo's geoWithin function only lets me hard code the polygons, but I would like to reference a collection of polygons.

See https://stackoverflow.com/questions/63162823/mongo-geowithin-error-polygon-coordinates-must-be-an-array

Recently we had a compact operation fail, and the mongod logs stated this was due to "eviction pressure" on the server. We have learned that this is a failsafe mechanism built into the compact command, but we would like to have a more verbose explanation of this failure mode in the logs to better understand why it failed and steps to remediate the issue.

From a user - A MongoDB in-memory emulator would help development against MongoDB in a completely isolated way. They deploy self contained applications for developers that don't have any external connections other than MongoDB. The customer found a community project, fongo, that does this, but it is not supported and trails development by a few versions. https://github.com/fakemongo/fongo. I would be happy to connect the users with relevant project managers

Support for wildcards or maybe even regular expressions in the database/collection name of a permission for a custom role.

We have a multi tennant setup, by storing every customer's data in its own database on the cluster. The applications we build span those databases, but every application has it's own permissions on a collection name bases.

instead of granting "find" permission to the "products" collection of all databases like "mongodbcom" and "somecompanycom", it would be nice if we coulf configure it like "find" permission to the "products" collection on the database matching /^[a-z]+_[a-z]+$/

Whenever a document is created within a collection to send a email to the account holder.