Database
302 results found
-
MultiTenant Abstraction
Just as a time-series collection in MongoDB 5.0 abstracts the underlying implementation of the bucketing pattern, customers who implement a multi-tenant model through separate databases per tenant run into the issue of too many dhandles and would benefit from an abstraction of the implementation of a collection-with-discriminator-field - they would be able to meet their internal compliance requirement of separate databases per customer, and would have minimal changes to their code.
1 vote -
Retrywrite error fixed in Mongodb 4.4
We have test the retry write in Atlas by using mongodb java driver in Mongodb 4.4 cluster. The error is similar to SERVER-53624(https://jira.mongodb.org/browse/SERVER-53624). The supporter respond the error will fix in Mongodb 5.0. We hope this error can also fixed in Mongodb 4.4
1 vote -
Make targeted query to a specific shard without using the shard key as part of query.
As of right now you need to use the shard key as part of the query to make a target query to a specific shard. Would like the ability to make targeted query to a specific shard without using the shard key as a part of the query.
Maybe one way of doing this is using index metadata to avoid scatter gather query and using that index meta data to instead make targeted queries on sharded clusters.
1 vote -
Easy Paging with offset
Paging is a common functionality for REST APIs. When implementing paging queries for large datasets skip and limit is often not an option. When using query filters with non unique fields, such as creation date there can be problems such as duplicate entities on subsequent pages. It would be great to be able to additionaly pass in an offset document reference, that would be used as a start in case the filter does not lead to a unique starting point.
so for example
db.test.find({"creationDate" : {$gte:ISODate('2021-08-27T07:25:00Z')}, {"offset":<ObjectId>).sort({"creationDate":1}).limit(20)1 vote -
Add a $median accumulator
There is the $avg operator that returns the average of a set of values. Why not a $median?
1 vote -
Provide global collection-aggregated latency stats
The global latency stats Server Status section currently aggregates all the latency information known to the server.
We have a need for the same information except aggregated by collection.
The actual command: db.serverStatus().opLatencies.
1 vote -
$lookup with the option to return only the first element
Often I have a $lookup and the next stage is a $addFields { $first: "" }} because I know the lookup will return only one entry. It'd be nice to have this option directly in the lookup, so it'd return the first object instead of an array. Thanks!
1 vote -
When using EA, auto update the list of cluster node members similar to what happens within Atlas
As we add new nodes, it requires us to update the URI. Would like a way to have this automatically update.
1 vote -
Would like the ability to restore a single zone based shard
If the idea that data is stored within a region (via zone based sharding) and they are "just" replica sets, why can't we just restore a single shard? Right now we have to restore the entire cluster.
1 vote -
Add build for Linux Alpine and Debian
A build in ARM support (Apple M1) for Alpine Linux (or Debian) is needed to run the mongocryptd process. Currently the official node docker images are available only in Alpine and Debian.
1 vote -
Support split documents on disk
As an application's functionality grows, if kept unchecked it is easy for average document sizes to grow simultaneously.
Large documents can have a significant impact on the performance of MongoDB. However, often the application doesn't actually need the entire document to service a request. Likewise, often queries are sent to MongoDB with a projection, excluding substantial (in terms of byte size) parts of the document.
MongoDB has no ability to optimise these projections (except for covered queries which are not always practical).
MongoDB should provide the ability to specify a "split" in a document such that the query planner can…
1 vote -
Creation of Custom Views
SQL based option to create view using multiple collections or databases
1 vote -
Ability to create the resume token based on oplog item
CHoose an oplog event to set the resume token for, instead of needing to run the change stream for system to create a resume token
Why: Concerns about many stream re-reading a full oplog if failure before finding first event
1 vote -
Cloning User/Roles along with Database
When cloning a Database it would be helpful if User/Roles could be cloned directly as well and carried over.
1 vote -
Pass document field to $loolup.from and $lookup.as
Suppose I have collection of documents { entityId, entity }, where entity is names of other collections I would like to make aggregation with lookup and be able to pass entity value to $lookup from and as
db.collection.aggregation([{ $lookup: { from: '$entity', let: { entityId: '$entityId' }, pipeline: [{ $match: { $expr: { $eq: ['$_id', '$$entityId'] } } }], as: '$entity' } }])
As of mongo v4.4.4 that seems not working.
1 vote -
Have a role that allows that user to control the schema of a collection
As a DBA or Data Architect, I want to be able to enforce data governance policies like schema control. Users of MongoDB cannot change the schema however DBA or named individuals have the ability to change the schema.
1 vote -
2dindex
geoIntersect queries on spherical geometries are not adapted to our use case. Our need is to retrieve a list of tiles intersecting a given area of interest (AOI) in a flat 2d geometry.
Classical geo-spatial databases (PostGIS and Oracle Spatial) support this kind of approach at no extra cost and we would expect the same from MongoDB.
In MongoDB , using a 2dsphere index forces us to implement a workaround adding an artificial margin to the AOI and making a post-processing to remove false positives. See attached slides for explanations.
Best Regards
1 vote -
Diacritic insensitive contains search on a single field
I would like to perform a "contains" query on a single text field in a case insensitive and diacritic insensitive way. I would like the query to have the performance of the field being in a text index by itself (assuming that this gives the maximum speed).
It is usually the case that the text index already exists for multiple fields. This means that a text search then has to be combined with a complicated (to make it diacritic insensitive) regex expression to find the correct results.
1 vote -
Add an option for $addToSet to use a specific field in the array for uniqueness
Currently, the $addToSet for upserting to an array checks for object equality (when the array elements are objects). We sometimes need to check for uniqueness based on a specific field of the object rather than the object as a whole, and the only way to do this is to force single-threaded operation and to use $pull and $push.
If there is a way to specify the field to check uniqueness for the $addToSet , we would be able to perform writes normally.
1 vote -
Extended JSON
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.
1 vote
- Don't see your idea?