Atlas Search
161 results found
-
3 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.
3 votes -
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 -
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 -
Ability to return all documents in a collection
I need to return all documents in a collection while boosting certain results which match my search criteria.
3 votes -
Allow retrieval of individual score from embedded document search
When using the emeddedDocuments operator to search you get a score per document, but not per embedded document. The aggregated score is either min/max/sum/mean but what I really need is the individual score from the embedded documents in order to further filter out the best matches.
3 votes -
add a setting to ignore the corpus term frequency for score calculation
indexOption:docs omits per document frequencies, but it still uses the corpus frequency.
it would be good to have a setting to ignore the corpus frequency as well
3 votes -
Atlas full text search should support searching all field types
Atlas full text search should support searching all fields types including text, dates, numbers and booleans.
Atlas full text search at present supports searching in text values only. e.g. Searching for "2022" will not pick up documents that contain 2022 in the number fields.
The functionality in it's current form does not have any way of searching for a given string value (which can be numeric, boolean or part of a date).
3 votes -
enable $and operator for multiple words in a search term (not only $or)
It seems a commonly needed ability to decrease the amount of results from a multi-word search query instead of expanding it, since the default operator for every word is $or. If there could be a built-in $and option it will be great. Thank you.
3 votes -
RBAC for Atlas Search
Atlas Search Indexes can only be managed via MongoDB credentials (Terraform or API calls), with required role "Project Data Access Admin" (see https://docs.atlas.mongodb.com/reference/api/fts-indexes-create-one/#required-roles ). It would be great if we could create/delete search indexes using database credentials, similarly to regular indexes.
Because of that constraint, we need to provision dedicated apikey for our application ; in order to create the relevant search indexes. However, providing "Project Data Access Admin" is too much of a security risk - considering the power of such role.
Would it be possible to have dedicated "Atlas Search Admin" role which would allow creation / updating…
3 votes -
wildcard path support for range operator
Currently wildcard path can be constructed to 4 operator(text, phrase, wildcard and regex). Some use cases will be there to use the wildcard path for numeric which can be used by range operator
{ a : { "6578ghg" : { value : "not 55" } } }
{ a : { "9578uhg" : { value : 55 } } }Above 2 document if we have dynamic mapping of search index and below query cannot be used as range does not support wildcard in path:
db.dates.aggregate([ { $search :{ index:"synonyms", compound:{filter:[{text:{query:"55",path:{wildcard:"metadata.*.value"}}},{range:{gte:55,lte:55,path:{wildcard:"metadata.*.value"}}}]}}}])Is there any plans/restriction for adding wildcard path support…
3 votes -
Support unstructured text entity recognition
We have unstructured text and would like Atlas Search to detect important entities so that we can use them for relevance and ranking
3 votes -
Include product versions in Atlas Search release notes
I am creating this feedback idea in customer behalf.
Customer suggests if adding product version numbers, for Atlas Search Release Notes pages. The page currently contains release dates, which does not provide sufficient information to debug Atlas maintenance upgrade execution plans.
Example: The release referred to
18 September 2024 Releaseon the main page https://www.mongodb.com/docs/atlas/atlas-search/changelog/#18-september-2024-release is related to Atlas seach (mongot) versionv.1.40.4.2 votes -
Allow type 'token' in embeddedDocument
Currently, string fields in an embedded document may be indexed as type 'string' using an analyzer, e.g. lucene.keyword. It is not possible, to index a string field in an embedded document as type 'token'.
Indexing as type 'token' is relevant for using a 'range'-operator in a query or to sort by a string field. This is would be very useful when working with sortable strings.
2 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 -
2 votes
-
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 -
Text Analysis for Field Mappings
Show how an indexed document and query terms get analyzed to produce tokens based on my field mapping configuration.
2 votes -
Allow indexing of synthetic fields
In order to work around some of the inherent limitations of the Atlas Search capabilities, it would be very useful if we could define and index arbitrary synthetic fields using any normal MongoDB functions & operators. All other Atlas Search capabilities (query, sort, etc.) should support these synthetic fields the same as any other.
This could possibly be implemented with a new field type and a custom analyzer that supports an aggregate pipeline on the input document and returning the field as its output. This is just an idea, there may be better ways to do it.
…{ "mappings": {2 votes
- Don't see your idea?