Database
287 results found
-
Low latency Change Stream for Global Cluster in Atlas
our event-driven applications need to publish events to Kafka triggered by Change Stream feature. It works perfect in replicaset MongoDB cluster.
However, after migrating to Global Cluster in Atlas, the Change Stream cannot keep low latency because of ordering reason among shards.
The latency may go up to 20 seconds when for a single change event.It would be nice if application can receive Change Stream from the single shard only (not care about ordering among shards) to prevent latency.
The idea is to pass "location" options when starting the Change Stream cursor.
3 votes -
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 -
updateMany limit
When porting an application backend from an RDBMS to MongoDB, we've spoken to two people who've are looking for a way to specify a limit on the number of documents in .updateMany(). I understand the behavior cannot be defined on a sharded cluster, but if we had a way to do this on an unsharded collection, that would help when dealing with these teams.
3 votes -
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 -
Arrow function support
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);
}
1 vote -
options for different compute configuration per shards
Can we have options for different compute configuration per shards?
1 vote -
Aggregate $accumulator 'Combine' stage for sharded collections
After the ‘accumulate’ stage has run against each document on a shard it would be extremely useful to run a script on the shard against the state to reduce the state down to something smaller before passing the final state over the network back to mongos for the ‘merge’. (Over in the Elastic camp they call this the ‘combine_script’).
Scenario:
I have a customer orders database sharded by the Customer ID (meaning all data relating to any specific customer is kept on the same shard - so customers don’t need to be ‘merged’ between shards). I can write an accumulator…2 votes -
4.4 to the EU on regular instance for development!
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??
1 vote -
Option to prohibit a non-voting member from becoming a sync source of a voting member
Hi,
Our proposition in a few words: add a replica set option to allow chained replication but with the following exception: a non-voting member cannot become a sync source of a voting member under any circumstance.
This proposition would allow chained replication for clusters having both w=majority writes and analytics nodes.
Right now, those clusters cannot safely enable chained replication, because under some circumstances, the non-voting analytics member may become the first secondary in a serial chain of replication. In that case, this node[*] slows down the replication process for all downstream secondaries. Higher replication lag translates to extremely slow…
3 votes -
Bundle rest service together DB
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.
1 vote -
EDGE
Localisation
1 vote -
Assign MongoDB roles to LDAP users
I would like to create a softlab and therefore give the possibility to a user to create collections in a database which is dedicated to him.
Currently, to do that I need to :
1. create a single-member LDAP group for each user
2. map this group to a MongoDB role authorizing the user's database.Create a group with a single member is conceptually useless. I want to avoid step 1.
My feature request : add the ability to assign MongoDB roles to LDAP users as well as groups.
Regards,
Jerome2 votes -
Allow custom autoscaling policies
Currently this is the following autoscaling policy in mongo:
Please note, if the next highest cluster tier is within your Maximum Cluster Size range, Atlas scales the cluster up to the next tier if one of the following is true for any node in the cluster:
Average CPU Utilization has exceeded 75% for the past hour, or
Memory Utilization has exceeded 75% for the past hour.The feature request is to allow a DBA to setup custom autoscaling policy
8 votes -
Conditional TTL index
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.
1 vote -
Include schema validation events in changestream payload
let's say my document has JSON schema validation like:
{ $jsonSchema: { properties: { phone: { bsonType: 'string' } } } }and the validation action is set to "warning", if I do a command like: db.test.insert({"phone":1}), I would like the warning message to be included in my change stream.
3 votes -
Support for Transaction Savepoints (Nested Transactions)
The ability to partially rollback transactions to a specified point.
2 votes -
collections under a document as in firebase firestore
collections under a document as in firebase firestore
1 vote -
Data masking policy
Implement Data masking similar to Schema Validation in Mongo so that customer can define a server-side data masking policy to mask the results of a query and a new role which will give explicit permission to users for reading unmasked data
4 votes -
Deny Privilege
Provide the ability to explicitly deny a privilege on a specific resource.
Example: Grant the privilege to perform the find action on all collections in the test database except "test.secrets".
4 votes
- Don't see your idea?