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 -
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 -
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 -
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 -
Sort by a specific array index
When creating indexes and sorting with "normal" queries, it is possible to index/sort on a specific array index (e.g.
foo.0.bar). I do this because the search results grid in our UI only has room to show the firstfoo.barresult, so it doesn't make sense visually to sort by additional objects which the user can't see.Since the new Atlas Search Sort syntax looks the same, I was hoping to do that with it as well, but it doesn't seem possible.
Example:
…[ { "xyzzy": "xyzzy", "foo": [ { "bar": "A" } ] }, { "xyzzy": "xyzzy", "foo": [2 votes -
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 -
Allow comments in JSON code
It would be great if we could keep comments in JSON generated items such as indexes (both MongoDB and Atlas Search)
2 votes -
Allow indexing of only part of a collection
Would be great to be able to create an Atlas Search index that only indexes part of a collection (like partialFilterExpression for a regular index). This would be valuable in situations where a collection is quite large (which would create a lot of unnecessary overhead) but only a small fraction of it needs to be searchable.
2 votes -
Grouping in $search
Add grouping capability to search so that it can be as performant as the search itself.
A separate group stage is not performant at all and is unusable.
2 votes -
Atlas Search vs find/match
Atlas Search is currently quite rigid and is not as awesome as find/match.
find/match supports a variety of operators that allow looking up documents in numerous ways and is meeting our requirements to be able to query using filters such as:
in, nin, eq, neq, gte, lte, all, any, gt, lt, size
These operators work with find/match for any and all data types including arrays. With arrays, find/match even does an exact match comparison which is one of our requirements.It would be great if we can combine the speed of Atlas Search with find/match features
2 votes -
Support for Index Partitions
When I reach Lucene's 2 billion document limit, I would prefer to partition my index instead of being forced to Shard my database.
2 votes -
Support Chinese Language Analyzer : Pinyin
PinYin IKAnalyzer Support
For most Chinese Speaking Customer,
https://github.com/medcl/elasticsearch-analysis-pinyin
Is also a popular analyzer that many of our customer is using it
2 votes -
Extending Range operator support to ObjectId values
If the Range operator supports ObjectId, it'll be really useful for the application that sorts or paginates data using _id, since _id is sorted by default.
2 votes -
Pre-Compiled Synonyms Collections
There are many instances where the synonym-related needs of users are similar. For instance, in the case of names, Robert, Rob, and Bob are considered synonymous for some use cases.
2 votes -
atlas search null
A string or number data type that has the value 'null' is returned and is not excluded even with filtering with query: 'null' entry. The $exists and $compound operators may benefit from excluding fields that have a value of 'null' but not exactly non-existent in a document.
2 votes -
Allow scoring with real word frequency (instead of word frequency per shard)
We are migrating from ES and there is an option when having a few documents to do a first query to return the term frequencies for all shards and then do the normal query using these frequencies to calculate the score.
The option is called "?searchtype=dfsquerythenfetch" and it's documented here: https://www.elastic.co/guide/en/elasticsearch/guide/current/relevance-is-broken.html.
It would be great to have a similar option in Atlas Search! Thank you
2 votes -
nested facets
in elastic we can do complex nested facet groups such as
"aggs": {
"resellers": {
"nested": {
"path": "resellers"
},
"aggs": {
"min_price": {
"min": {
"field": "resellers.price"
}
}
}
}
}It would be nice to see the same functionality in atlas search
2 votes -
Configure Alert "Insufficient disk space to support rebuilding search indexes" via API
Currently, it's not possible to configure the alert "Insufficient disk space to support rebuilding search indexes" via API (and therefor also not by terraform).
When setting the respective eventTypeName "HOSTDISKSPACEINSUFFICIENTFORSEARCHINDEX_REBUILD"
I get the following response:
400
request "INVALIDENUMVALUE"
An invalid enumeration value HOSTDISKSPACEINSUFFICIENTFORSEARCHINDEX_REBUILD was specified.The API should support this (and any other alerts configurable by the UI).
2 votes -
Configure Search Relevance or Results Ordering in the UI
I want to be able to configure search relevance or the order of results with a n Atlas UI module and no code.
2 votes
- Don't see your idea?