Atlas Search
149 results found
-
Allow the ability to test Atlas Search locally
We need text search to "somehow" work locally and ci.
We've a multiregional team and development has to continue if there are internet problems in one of our offices.
Our workflow consists of :
unitTest using in-memory-mongodb
local testing, using the developers local mongo instance
test env testing with a QA team (using atlas, but <30m)
production launch
With the current feature set, the first time we can test a feature is on production. Even if low-tier availability was there the other two issues are blockers as we won't just ditch TDD for textSearch.
352 votesNow in Public Preview: Introducing a Local Experience for Atlas, Atlas Search, and Atlas Vector Search with the Atlas CLI
Please feel to reply with feedback or leave comments. Happy to connect directly and include your team in our Early Access Program to provide additional help.
-
Allow $search to be a later stage in the aggregation pipeline
Currently $search is required to be the first stage in the aggregation pipeline. It would be more intuitive if we could use after other operators, such as $match.
81 votes -
Support Partial Indexing
We have a large collection but would only like to index the most recent entries, which would reduce the amount of space and resources it would take to index and query.
42 votes -
Support for nested datatype search
It appears that Atlas Search does not yet support nested documents in arrays like MongoDB
https://docs.mongodb.com/v4.2/reference/operator/query/elemMatch/
39 votes -
Target $search queries to specific shards
Currently, sharded $search queries are scatter-gather queries and they cannot be targeted to specific shards. This is an enhancement request to target $search queries to specific shards, and thereby make them more efficient/performant.
27 votes -
geoWithin metadata reporting searchDistance
Using geoWithin in the $search aggregation pipeline lets me use the search indexes, but it doesn't let me see the distance. I'd love to have a distanceField or perhaps a $meta that reports searchDistance similar to the one we have for searchScore
18 votes -
Support Decimal128
Enable indexing and querying of near and range operators for Decimal128.
18 votes -
Hierarchical/Multi-Level filters/facets.
As a user, I'd like to be able to compute faceted counts on multi-levels of categorization.
17 votes -
Atlas Search on serverless instances
Hi,
I'd like to use Atlas Search on Atlas Serverless.
16 votes -
Allow faceting for embeddedDocuments
At the moment embeddedDocuments does not allow number or date faceting.
In my opinion, this does not make the operator useful, since Faceting is now the standard for every search.
16 votes -
Atlas search to provide the ability to query number (long/double) fields
When querying mongo using atlas search, today it requires that the query parameter be a string. Ideally, I would like to be able to also search using numbers. Our stakeholders want the ability to type into a dropdown select field , type a number, and have it pull back a list of data.
Today, we are using atlas search to query against a multiple set of fields, and pull back the most relevant results. It would be nice to include number fields as part of our index in order to allow those same stakeholder the ability to query by the…
15 votesAdmin mistake! Long Numbers are also still unavailable. Reopening this and I am sorry for the confusion.
-
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.
-
Add storedSource parameter to atlas admin API search index create/update to use with terraform
Right now it is impossible to create atlas search index via terraform with "storedSource" parameter. This brings a lot of inconvenience and configuration-related bugs.
Related issue
https://github.com/mongodb/terraform-provider-mongodbatlas/issues/871
13 votesWork to address this has been scheduled.
-
Support more complex groupings in facets
The facet collector groups results by values or ranges in the specified faceted fields and it currently returns the count for each of those groups. However, besides counting, it would be good to have facets also support more complex groupings, such as averages.
This is a feature request to have facets support complex groupings, and expand its capabilities beyond generating counts for various buckets.
12 votes -
Return results from within arrays
I have a document that looks like this:
{
shoppingList: [ { name: "red hat"}, { name: "green shoes"} ]
}I would like to query $search for "green" and return {name: "green shoes"} instead of returning the entire document.
11 votes -
Support ObjectID as a datatype for search facets
I'm really interested in using search facets to boost search performance, but one of the fields that I want to filter by is an ObjectId.
I believe the only supported facet types are [date, numberFacet, stringFacet].
10 votes -
Analzye Endpoint or Analysis Screen
Please show how an index is analyzed based on a given index definition.
10 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 -
$bucketAuto for number facets
As a developer, I would like to have functionality for NumberFacets similar to the $bucketAuto operator, so that I can define the number of buckets I want instead of setting the boundaries myself.
This function is helpful in situations where you don't know the boundaries or can't calculate them easily.
Example:
myNumberFacet: {
type: 'number'
path: 'path.to.my.field'
buckets: 1000
}9 votes -
Errors When Querying Non-existent Indexes
I renamed the first index I created when testing out the feature so it wasn't default, and spent quite a bit of time debugging why my queries were returning no documents. As it turns out it the default index that it queries if not defined is "default", but that index didn't exist. Instead of throwing an error about querying a non-existent index, it just returned an empty array which was very frustrating
9 votesThis work is under review and research.
- Don't see your idea?