Atlas Search
158 results found
-
Allow the option to mention the number of search results needed
I would like to get only the top scored 1000 or 2000 records while doing the search. Currently this is 2 step process : $search and then use the $limit stage.
5 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 -
Query_syntax operator should support lucene syntax
At the moment the query_syntax seems to have a custom syntax. It looks similar to lucene syntax but is not the same.
There are a few differences to azure and elastic and I don’t understand whether I am doing something wrong or not.
What all three service have in common is that they are built on top of lucene, therefore I though that the querystring operator uses the lucene query syntax as it seems to be done by elastic and azure: https://lucene.apache.org/core/29_4/queryparsersyntax.html
Documentation about the elastic query string query can be found under: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html
There are a few…
2 votes -
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.
90 votes -
Total Document count on Filter
It's a very small feature but very useful with respect to use case, whenever someone filters on Atlas nowhere it shows the total number of result we got, till we didn't reach the last page so it's very useful if we can see the total number of records at least after filtering or it will be great if it is visible on each page.
4 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 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.
61 votes -
Improve error message when index definition exceeds 3KB
hen you create an index definition on the free plan that exceeds 3KB you get the following message:
{"detail":"A tenant FTS index may not exceed 3 KB in size.","error":400,"errorCode":"TENANTFTSINDEXTOOLARGE","parameters":[],"reason":"Bad Request"}
The message could be clearer. I had no idea what it meant and had to search the docs for that.
The limitations are described here: https://docs.atlas.mongodb.com/reference/atlas-search/limitations/
1 vote -
Add other operators (range/TO, NOT) in queryString
I like lucene query string syntax (https://lucene.apache.org/core/8_10_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package.description). I think it is more human-readable. So, please add the range operator to it and if it's possible, add other ones like NOT, regex, boosting, proximity and fuzzy.
If it's hard, please focus on range and NOT1 vote -
Enhanced alerting for Atlas Search
I am looking to set up alerts for the following criteria related to Atlas Search:
- Alert and metrics based on search index queue size (when we expect results to be slow to appear)
- Alert when a search index is being rebuilt (when we expect degraded performance and potential downtime) - there are already alerts included by default for Search Index Build Complete, and Search Index Build Failed, could it just be a new alert for Started?Thanks
1 vote -
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.
363 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.
-
Add Atlas Search metrics into integration with Datadog
Problem Statement,
Atlas Search metrics (https://docs.atlas.mongodb.com/view-atlas-search-metrics#atlas-search) are not sent to Datadog (Datadog's MongoDB Atlas integration (https://docs.datadoghq.com/integrations/mongodb_atlas/)).Proposal,
Add Atlas Search metrics to Datadog integration (start sending Atlas Search metrics from Atlas to Datadog).4 votes -
Allow queries with $search to be covered by the Lucene indexes without loading from disk in Mongo
If the fields to be filtered on or projected on are all in the Lucene index, it would give the best latency to be able to return the data from the Lucene index only, and not have to separately look that data up from the Mongod
4 votes -
API to list all Atlas Search Indexes configured across all collections in the cluster
Currently, there is an API to list all Atlas Search indexes configured for a specific collection. However, there is no API that lists all Atlas Search indexes configured across all collections across all databases, in a particular cluster. The Atlas UI shows this, but the Atlas API does not have that functionality.
This is a feature request to add the API capability to list all Atlas Search indexes configured on all collections in a cluster.
2 votes -
Support Decimal128
Enable indexing and querying of near and range operators for Decimal128.
27 votes -
Autocomplete with `fuzzy` scores all results as `1`
Using autocomplete with the
fuzzyoperator returns results, but they are scored all with the same value (1). This has been reported a couple times in the developer forum as well:https://developer.mongodb.com/community/forums/t/fuzzy-autocomplete-score/13341/4
This can make it difficult to process and rank results on the client side, especially for high volumes of returned documents. It would be helpful if autocomplete + fuzzy would support relative scoring.
3 votes -
Analzye Endpoint or Analysis Screen
Please show how an index is analyzed based on a given index definition.
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.
18 votes -
Allow ability to exclude specific fields from Atlas Search
In order to reduce index size and improve performance, we should be able to exclude specific fields from the Atlas Search index.
2 votes -
Leverage atlas search indexes in find and count operations
Currently the documentation wasn't outright clear that Atlas search indexes can only be leveraged through Aggregation operation. It will be great if we can leverage them in find and count operations as well.
1 vote
- Don't see your idea?