Database
320 results found
-
Decouple "insert" privilege from implicit collection creation
MongoDB currently allows a user with the insert privilege on a database to implicitly create a new collection by inserting into it — even if the user lacks the createCollection privilege. This behavior makes it difficult to enforce strict access control policies, particularly in security-conscious or regulated environments.
In contrast, traditional SQL databases like PostgreSQL and MySQL enforce a clear separation:
The INSERT privilege applies only to existing tables.
A separate CREATE privilege is required to define new tables.We request that MongoDB introduce the ability to decouple insert from implicit collection creation, such as:
A new action like "insertExistingOnly",…
1 vote -
1 vote
-
Coordinate Releasing Better
When Mongo releases a new version, the downloads, release notes, and version selection in the support portal are never in sync and sometimes out of sync for weeks.
An example right now is 7.0.20. It has been out for a while. If I update via my OS's package manager, I get 7.0.20. Is 7.0.20 in the release archive download page? No. Does it have any published release notes? No. Is it selectable in the Versions list at support.mongodb.com? No. In fact, 7.0.19 is still not selectable there.
This is very frustrating and causes a lot of workflow/process issues. For example,…
2 votes -
Add Option to Disable Specific Metric Groups in FTDC
https://jira.mongodb.org/browse/SERVER-103431
This is a feature request (not a bug) to enhance FTDC by allowing users to disable the collection of specific groups of metrics.
Currently, FTDC collects a wide array of metrics including systemMetrics, which may contain data not always needed (e.g., disk stats from mount points that are irrelevant to the workload). This can generate unnecessary overhead or clutter when analyzing diagnostic data.
Proposed Enhancement:{}
Introduce support in FTDC for selectively disabling or adjusting the collection interval of particular groups of metrics, such as:
systemMetrics
serverStatus.connections
Other major metric groups (as applicable)This filtering should ideally support:
Disabling collection…
6 votes -
Validation should support default values
Various users feel that validation should support default values. See, for instance:
https://www.mongodb.com/community/forums/t/support-default-value-in-schema-validation/319684
https://www.mongodb.com/community/forums/t/setting-default-values-in-data-schema/84112 votes -
Support default values in validation
Many MongoDB users feel that default values should be supported in validation. See, for example:
https://www.mongodb.com/community/forums/t/setting-default-values-in-data-schema/8411
https://www.mongodb.com/community/forums/t/support-default-value-in-schema-validation/3196841 vote -
Provide a dictionary for matched/modified/deleted counts for bulk writes
Current bulk write operations provide only aggregated counts that look like this:
{
acknowledged: true,
insertedCount: 0,
insertedIds: {},
matchedCount: 2,
modifiedCount: 2,
deletedCount: 0,
upsertedCount: 0,
upsertedIds: {}
}
All these operations are processed individually by the server, even if out of order, meaning that the current Mongo DB code aggregates these individual counts in order to present them in the structure above.This aggregation, however, makes it impossible to use bulk writes in the same way single updates and deletes can be performed, which significantly slows down mass updates.
Consider updates of versioned documents - one can issue…
1 vote -
x509 Authentication Supports Multiple CA's
I work for a large entity with a complicated security certificate structure where we are unable to create certs with specific CA's but rather they are issued to us by request and thus we don't always have control over the root or intermediate CA in the chain.
We have a situation where server certificates are signed with one CA but client certificates are signed with a different CA. All the CA's are installed and trusted in our Windows certificate store, but the current limitation of Mongo is it only supports a single CA.
Would it be possible for Mongo to…1 vote -
Dont Deprecate LDAP in future Major Version releases.
we have everything configured with LDAP including Ops manager agents/bind id's/DB ID's etc. We have so much dependency on LDAP which helps us in many ways including rotation of passwords in CyberArk, No dependency of Single passwords etc.
Kindly help not to deprecate LDAP features.3 votes -
mongodump - add support for nsInclude/nsExclude
Currently mongodump supports the excludeCollection/includeCollection options but this requires the use of the --db option. It would be useful if mongodump was able to dump all databases, as it does by default, but also be able to specify a collection or collections not to dump.
2 votes -
Maintain database ID/Password profile inside database
Requirement is to maintain database id/passwords with standard details inside database like (Lastlogin date/ passwordchangedate) and control of passwords related how many failedloginattempts/passwordlifetime/passwordcomplexity/passwordlocktime/passwordreusemax etc
4 votes -
Allow the ability when NVME cluster to autoscale up based on CPU and Memory
To provide autoscaling capability for MongoDB NVME clusters based on CPU utilization and memory metrics. This feature would automatically provision additional resources when predefined thresholds are reached, ensuring optimal performance during usage spikes without manual intervention.
Currently, MongoDB Atlas NVME-based clusters require manual vertical scaling, which leads to:
- Performance degradation during unexpected high-load periods
- Inefficient resource allocation requiring constant monitoring
- Potential application downtime during scaling operations
- DevOps overhead for continuous capacity planning3 votes -
Leveraging Group By/Distinct Query to use regular Index
When using Group By or Distinct queries on database, provide the ability to leverage existing index
i.e these queries today will miss using existing index
db.collection.distinct("field")
db.collection.aggregate([
{ $group: { _id: "$category", count: { $sum: 1 } } }
])2 votes -
Disallow new connections that don't specify an appName field
Currently as a DBA it's sometimes hard to identify which service is causing load on a shared cluster/database. Some people connect for adhoc workloads but don't specify an appName making it hard to track back to the owner. It would be useful to require appName for connections to a cluster to enforce this behavior.
2 votes -
Certificate "friendlyName" (windows system certificate store)
mongod.exe:
currently there is only support for "subject" and "thumbprint" to select the certificate from the windows certificate store.
Is there a plan to implement the "friendly name" of the certificate as well?example mongod.cfg:
..
tls:
mode: requireTLS
certificateSelector: friendlyname=FRIENDLY-NAME1 vote -
deleteMany() execution automatically disable the balancer on sharded clusters
deleteMany() execution automatically disable the balancer on sharded clusters
1 vote -
Execute $group on shardPart instead of mergerPart
Basically what is described here: https://www.mongodb.com/community/forums/t/how-to-enforce-mongodb-to-execute-group-on-shardpart-of-the-execution-plan/267560
When running covered count queries that could be aggregated independently on the shards, there is still a lot of overhead due to the fact that shards have to report documents with _id to
mongosIt looks like this is happening for count queries that use $limit stage, but not for count queries without it
1 vote -
Support for proxy protocol on mongod
Hi,
I have mongodb database server running as a container on kubernetes and i have istio as ingress, but i need proxy protocol in order to preserve source ip, because without proxy protocol the client ip that arrives in mongodb server is the ip from the istio ingress gateway.
I know mongos already supports it for sharded clusters, but would be very helpfully if mongod could support proxy protocol as well.
1 vote -
Option Renaming Time Series Collections
Ability to rename TS collection . We need it for migration history data to TS without downtime during conversion.
1 vote -
Support retrieving all connections info from clients to mongodb
Support retrieving all connections info from clients to mongodb, not just those running commands returned by currentOp(). OS command netstat can return all ip info, but it does not contain the relation ino between ip and database such database name and user. It's a common function in relation database, e.g. 'show processlist' command in mysql. And it's useful when we try to migrate to a new MongoDB cluster, we need to find out all the clients connected to the original mongodb.
1 vote
- Don't see your idea?