Database
287 results found
-
Exclude PDB files from installation
mongod.pdb is nearly 1.0GB, mongos.pdb - 0.5GB
Since these fils are not necessary for the server to function properly, they should be optional, e.g. provide a checkbox to exclude them during installation.
1 vote -
DB Snapshot triggers when RDS Snapshot starts.
Looking for a feature regarding DB Snapshots, so that we can configure a Snapshot Policy to be triggered whenever a specific AWS RDS snapshot starts (for the daily schedule).
Thank you in advance.
1 vote -
define the random seed manually, for $rand and $sample
It will be great if an additional paramater to define the seed for $rand and $sample could be use.
2 votes -
Lock on session start level with provided keys
Scenario:
Parallel DB updates with transactions on multiple collections that use same documents.
Example: Calculate some common stuff to embed it in extra collections to avoid lookups.Problem:
Lock and timeout on documents uses up valuable time and performance.
Also lock conflicts produce a huge amount of exceptions that need to be handled.Idea:
Key-based sessionsExample:
Session A with Keys 1 and 2 is started.
Session B tries to start with Key 1. Key 1 is locked with Session A. Session B waits till Session A is finished.In this case transaction doesn't start with updating and failing. Waiting…
7 votes -
Vector Search
Provide Vector Search capability in MongoDB enterprise edition for On-premise deployments.
1 vote -
Allow live migration using private interface
There should be an option to live migrate data via a private interface instead of public one. With VPC being peered, it would be a great option to avoid exposing database to the public interface (even if it's specific set of IPs). This can resolve concerns of many customers who are following or need to follow some short of compliance on their end.
1 vote -
an aggregation stage to load data to DRAM for the fields that are only requested
When we use $project stage, it loads whole document from disk to memory (if not in working set). Because of this, When we create a data model, We have to create separate collection if the field is not required in frequent access of data. Creating a view is an option, but what if $project itself or $project with some argument in it, or a new pipeline stage or operator gets introduced which fetches the data from disk only for the fields specified instead of loading whole document.
With memory mapped file, retrieving fields specified alone would not be simply possible…
1 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 patterns quickly, so we have profiling enabled in production on a busy system and we do real-time analysis on the the system.profile collection. This works fine and the performance hit is acceptable but our system logs on disk grows a lot.
Please make it possible to configure if profile logging should go to disk, collection or…
8 votes -
Allow to define access to DBs/collections by prefix or pattern.
Please extend ACL to support prefixes (or regex) in the database name/collection.
Currently only allowed ALL (when empty string provided) or exact db/collection matching when provided.Use case: Several services are using the same cluster but need to be isolated. Every service can get readWriteAnyDatabase but only to databases prefixed by some prefix.
Services need to create new databases on the fly, so it is not possible to define a list of databases upfront.For example - rwRoleForService1 allows "update", "insert", and "remove" operations only on databases prefixed by "service1-" (sevice1-db1, sevice1-db2, ....)
{
role: "rwRoleForService1",
privileges: [
{
{…7 votes -
When was last backup/mongodump ran on databases or database backup history
How can get detail of last backup was taken using query. Its very hard to get into log file and see the history of mongodump. Just like other database tool mongodump history can be retrieved via query instead mongo log file.
I know get the detail from ops manager if using enterprise only but what if we are using community edition.
If you include this feature it will very helpful for DBA to get the details juts like other database tools available in market.
1 vote -
Tool for score data model
It would be great to have a tool which can scores a data model from a specific database. I mean, I could allows this tool to scan a database model and score this data model based on best practices, patterns and anti patterns. It could also generates a list of problems and suggestions for improvement.
This tool could be used on CI pipelines near to the unit tests and the main goal is to avoid release new features using a bad data model.
2 votes -
$group all fields
$group should have the ability to allow specifying all fields in a document (without explicitly defining them all, which can lead to duplicating dozens of lines just to do "key: $first")
This will help users that use $unwind and then want to $group the results without having to do a subsequent $lookup and $mergeObjects (or similar) to get the final document structure they're looking for.
1 vote -
Amazon Linux 2023 Support for MongoDB 6.0 and OpsManager 6.0
Amazon Linux 2023 is supported in rapid releases from 6.2.0 and will be supported in the upcoming 7.0 release of MongoDB, however it appears there is currently no plan to support AL2023 for the 6.0 release of MongoDB. Can support for AL2023 be added to the 6.0 branch for both MongoDB and OpsManager?
1 vote -
Support indexes on single array elements (e.g. "MyArray.0")
Currently, if I create an index on an array field and specify an element number ("MyArray.0"), the system still indexes the whole array as normal.
Normally, this might increase the index size but at least it's still useful when querying MyArray.0 later.
However, it would be better to be able to index individual numbered elements in cases like compound indexes where I might need to check whether two arrays are non-empty, and I can't use a compound index for a query on MyArray.0 and MyOtherArray.0 at the same time due to the multi-array limitation.
For MongoDB folks with access to…
1 vote -
Collection which stores last login date_time for the users
Are you please able to store the last login date_time for the users which exist either in admin database or $external database in a collection of admin database of that cluster or opsmanager database which manages the clusters?
I have a requirement at my end - is to find the users who havent logged in for 60 days, , their roles to be revoked. And, ultimately delete the users who dont have any roles attached after a fixed period of time.
I do undertsnad you store the login details in audit logs. But that would be a tedious process at…
1 vote -
Add timestamps to user documents
Most database technologies store this metadata by default.
Because the expected data volume and change rate of this attribute will most probably be low, there should be no reason of not storing this information.
Of course this information might already be available in audit files, but first: auditing isn't enabled by default.
Second: most database users won't have access to this file/info and third: most users won't expect this info in a separate file (reminder, MongoDB recommends to store the data where it belongs when it comes to "data/schema modelling", so the metadata of a user document should also be…10 votes -
Metadata for collections
I would like to be able to store metadata about a collection such as a description or link to sources, along with the name of the collection.
1 vote -
Flatten arrays in group stage
Have group operators to flatten document arrays into a single one with or without repeated elements.
So ->
doc1 = {arr: [1,2,3,4], gr: "group"}, doc2 = {arr: [5, 6, 7, 8], gr: "group"}
{$group: {id: "$gr", arrays: {$***: "$arr"} } }
=>
{id: "gr", arrays: [1, 2, 3, 4, 5, 6, 7, 8]}2 votes -
tail queries functionality
We'd like to log the underlying MongoDB queries issued against the database. Similar to https://github.com/mrsarm/mongotail but something official
1 vote -
Change stream Monitoring/Aletring in management
how to monitor change stream activity per namespace
1. Number of Change streams per namespace
2. Set + Manage the allowed number of change streams
3. A metrics UI tab for OpsManager.
4. Alert if the number of change streams exceeds the set limit.This will assist in managing the cluster and also avoiding any issue that may arise from highly demanding change streams that take up RAM and compute.
1 vote
- Don't see your idea?