159 results found

1. Allow to create Atlas Search index on a not existing collection

   Currently it is not possible to create an Atlas Search index on a not existing collection, this makes more complicated to automatise the index creation on new clusters (e.g. via terraform).

   Would be nice to allow the implicit collection creation when creating an Atlas Search Index.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Percolator/reverse search

   Ability to store queries that allow you to supply a document and return the queries that match it.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. 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 / deleting search indexes ?

   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… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. 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 thing that work differently:

   1. The Atlas query_string does not support fuzzy operator like helo~.
   2. The Atlas querystring cannot search in multiple fields, because “*” is not supported as a defaultpath.
   3. The Atlas query_string does not seem to support the lucene syntax at all.

   This makes migration harder and the user cannot use the syntax. I got it working with a custom converter so it is technically possible, but it would be better if Atlas search would just support it:
   https://github.com/SebastianStehle/MongoSearchTest/blob/main/Mongo.LuceneQuery/LuceneQueryVisitor.cs

   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… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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.

   91 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   9 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. 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 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… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. 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 NOT

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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.

    370 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    37 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    started  ·  Elle responded

    Now in Public Preview: Introducing a Local Experience for Atlas, Atlas Search, and Atlas Vector Search with the Atlas CLI

    
    

    Relevant docs found here.

    
    

    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. 

13. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Support Decimal128

    Enable indexing and querying of near and range operators for Decimal128.

    30 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    10 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    under review  ·  AdminAmy (Admin, MongoDB) responded

    You can now transform documents for Atlas Search, enabling you to index and query Decimal128 fields as a Double. See how here.

16. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Autocomplete with `fuzzy` scores all results as `1`

    Using autocomplete with the fuzzy operator 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

    https://developer.mongodb.com/community/forums/t/trying-to-understand-atlas-search-autocomplete-result/13819

    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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. 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.

    19 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Analzye Endpoint or Analysis Screen

    Please show how an index is analyzed based on a given index definition.

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Please add lucene.kuromoji

    I just happened to know that full-text search feature is available in MongoDB Atlas. Greatly appreciated if lucene.kuromoji is added to a list of language-specific analyzers. Currently, there is only a generic Chinese, Japanese, and Korean analyzer.

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating