Atlas Search
149 results found
-
2 votes
-
Atlas Search aggregation pipeline TypeScript type definitions
It would be so much easier to write aggregation pipelines if we had type checking and type hinting.
At this moment we can pass any JSON there. There is no driver or library that would check if it's correct or that would type check the input.
I'm attaching some screenshots that show how it could work.
2 votes -
Ability to Upsert an Atlas Search Index
Currently, it is possible to use
createSearchIndexandupdateSearchIndexto create and update search indexes, respectively. It would be beneficial if theupdateSearchIndexallowed for upsert functionality, so that if the index does not exist, it can be created. This functionality would be useful in certain scenarios where the indexes are created (if they don't exist) or updated (if they do exist) programmatically, which have to rely on implementing a custom if-else logic by leveraginggetSearchIndexes().3 votes -
Provide the ability to auto-scale dedicated search nodes
Currently, dedicated search nodes in Atlas Search cannot be auto-scaled. This is a feature request to introduce the ability to auto-scale dedicated search nodes.
4 votes -
Increase the disk size limit of 3.2 TB on Search tier.
Atlas search tier limits the disk size to 3.2 TB even on the highest search tier S110.
2 votes -
Compatibility with shard reduction
We are using Atlas Search (as a sidecar process) and aren't able to reduce the number of our shards without causing downtime to Atlas Search. A shard mechanism that's compatible with Atlas Search is necessary for us to optimize our costs.
2 votes -
Mutli-select faceting / facets should not affect their own filter field
I want to build multi-select facet without having to run separate queries to calculate bucket counts for each active filter. Described in detail here: https://yonik.com/multi-select-faceting/
9 votes -
allow atlas search for serverless instances
As of now, atlas search is not allowed for serverless instances, but many people using serverless instances and they atlas search to perform some advanced search queries.
1 vote -
expose json schema when doing dynamic mapping
It would be really helpful to see the json schema when doing dynamic mapping so I’ll be able to alter it according to my needs. Building everything from scratch takes a lot of time.
I use the json editor. I want to index a lot of fields and some of the fields contains arrays and documents that I want to index as well. Writing the schema to index all the fields takes a lot of time. When I do dynamic indexing I know that you have the schema in the backend. It will be very helpful to expose this schema…
2 votes -
1 vote
-
Atlas search Index is not updating.
Each time I perform CRUD operations in my collection, the Search Index doesn't update immediately. Instead, it takes a considerable amount of time. This issue significantly hampers the progress of my project. Any suggestions for improvement would be greatly appreciated.
1 vote -
1 vote
-
Support highlights in embeddedDocuments autocomplete
According to docs, currently it is not possible to get highlights inside embeddedDocuments, in autocomplete requests.
This makes array of objects (embeddedDocuments) autocomplete unusable in our use case.
3 votes -
Non-sequential or Deep Pagination
I want to be able to paginate results in non-sequential order, e.g. Skip from page 1 to 5, or skip from first to last page of results
1 vote -
Add Atlas Search for Enterprise Advanced
Due to customer/project constraints, I need to have the ability to use $search to query millions of historical data records with regex and wildcards queries at real-time, on a Enterprise Advanced environment.
The data cannot be exported to Atlas and it cannot depend on Internet connection, so the functionality must be On-Premises only.
3 votes -
Dedicated search nodes
Currently, Atlas Search (mongot) is collocated with Atlas (mongod) on the same database deployment. Today, I have to size their workload based on both search and database requirements, which introduces the possibility of resource contention between their database and search deployment. I'd like to scale my search deployment independently of my database deployment.
13 votesWe have a private preview available for this feature. Please enroll in our early access program here ( https://www.mongodb.com/dasal ) if interested or reply to this update.
-
Allow sort by boolean fields
When creating indexes and sorting with "normal" queries, it is possible to index/sort on a boolean field. I was hoping to do this with Atlas Search Sort as well, but it only supports date, number and token (string).
While workarounds are available (using custom scoring), these are not easily combined with multiple sort fields and make programmatically building a query vastly more complex.
2 votes -
knnBeta Limitations and Syntax
I tested the new knnBeta operator today and it worked so far.
Can we expect the current operator limitations to be gone by release?
The current limitations make it virtually impossible to use the knn operator as a replacement for previous text operators (like text).
I would prefer the filter parameter to be omitted and knn not have to be a top-level operator.1 vote -
Allow aggregate pipeline on input documents before Atlas Search indexing
If Altas Search allowed us to apply an aggregate pipeline to input documents before they are sent to Atlas Search for indexing, it would open up a TON of new possibilities not currently supported. We could do data transformations, type conversions, synthetic fields, etc.. I've opened up a number of other suggestions for these things, but an input aggregate pipeline could solve all of them in one "easy" solution. Since aggregate pipelines already exist and are deeply embedded in MongoDB, I'm hoping it would be trivial to implement as well. Simply pick up one or more new documents to be…
2 votes -
Atlas can be configured to raise alert notification when the Atlas cluster already scales to the max tier.
Atlas can be configured to raise alert notification only when the Atlas cluster already scales up to the max tier allowed. This can be help to avoid notification spams which does not require operation team actions and focus on the critical resource consumption alerts like cpu, memory, disk IO.
1 vote
- Don't see your idea?