Database
324 results found
-
I just wanted to say Good job!!!
Appreciation
2 votes -
AWS IAM Role integration with MongoDB On premise
We are planning to integrate AWS IAM Roles/Users with MongoDB On-premise for password-less authentication. So the authentication happens through IAM Profile. However, we noticed currently MongoDB on-premise doesn't support AWS IAM Role integration. This is a blocker. We want the authentication would happen through AWS IAM Profile rather than Standard Credentials.
This would eliminate or significantly reduce the use of Database Credentials while tightly integrating with AWS Services. Simultaneously, applications can securely connect to MongoDB via AWS Profile.1 vote -
array length as computed to be indexed
in some cases, I need to filter only docs with specific (or range of) sizes of nested arrays.
it will be good if I can configure 'automatic index' to keep the length of the array, based on the field name I will provide to the index, and then I can easily get the docs.(now I need to add and maintain this field on myself or with trigger)
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…
4 votes -
session
The possibility configure what network or IP the user can be connect in the cluster in the mongo atlas.
1 vote -
Allow disabling auto removal for capped collections
Capped collections work as a circular buffer - when adding new documents after the size limit is reached, old documents are removed.
I would like to have an option for the collection, where this behavior can be changed - instead of removing old documents, the insert should fail with a specific error (eg: collection full). This would allow implementing log-rotation, by creating a new collection whenever the old one is full.
My motivation:
I have two services, one creating documents (events), and another one processing them. I'm looking for a reliable way to:
- process all documents from start, without…1 vote -
add index on oplog collection which will avoid full collection scan where change stream enabled , as of now full scan causing high cpu
add an index on oplog collection for change stream to avoid full collection
1 vote -
placement of mongosh,mongo tools and mongo binary inside core bin
Hi Team,
Hope you are doing great!
Didn't understand the purpose of keeping mongosh,mongo tools and mongo binary separately, can't this be place in a single rpm/tar file so that it can be easy the installation process.
As per the current :
Mongo binary location :/var/lib/mongodb-mms-automation/mongodb-linux-x86_64-6.0.8-ent/bin
Mongo Tools location :
/var/lib/mongodb-mms-automation/mongodb-database-tools-linux-x86_64-100.7.4/bin
Mongosh location :
need to keep this file in separate location and access the mongodh. mongosh-1.10.1-linux-x64.tgz
Thank you
1 vote -
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 -
Allow rotation of Arbiter TLS certificates when authentication is enabled
Mongo arbiters do not support using db.rotateCertificates(), because they do not possess the internal table of user and role mappings used for authentication.
Add functionality to enable rotation of these certificates.
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 -
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 -
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 -
Vector Search
Provide Vector Search capability in MongoDB enterprise edition for On-premise deployments.
1 vote -
$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 -
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 -
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.mongodb.org/browse/SERVER-1460), and usually prompts a response like "just use integers". With the addition of time series collections however, where the concept of time is integral to database functionality, I think it's time to reconsider adding a type with at least nanosecond precision timestamp support. Date's millisecond resolution is woefully inadequate for a number of relevant use cases,…
10 votes -
add IO throughput related fields to 'serverStatus' output
There is no IO throughput related fields in the result of serverStatus, instead in FTDC this is available in the disk metrics.
Need it inserverStatusoutput so that we can monitor it.3 votes -
Handle Daylight Saving Time when $densify is used on a date field
When using "day" as "unit" for a $densify pipeline stage on a date field, the date is always advanced of 24 hours. This is however not always the expected result in timezones in which the year has one 23-hour and one 25-hour long day, because of Daylight Saving Time.
It would be useful to have the possibility to pass an optional timezone parameter in the $densify stage and, when present, have the stage account for these exceptions when appropriate.
Here follows an example.
Assume we have a collection containing the following documents:
…db.densifyDateExample.insertMany([ {_id: "a", d: ISODate("2022-10-28T22:00:00Z")}, {_id: "b", d:9 votes
- Don't see your idea?