55 results found

1. Deploy Atlas Search from Terraform

   Add the necessary resource types to the mongodb_atlas Terraform provider to enable Atlas search indexes to be deployed by Terraform. This is needed as we need MongoDB apikey to call the API.

   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 →
   completed  ·  Elle responded

   We’ve released an integration with Terraform – feel free to utilize this documentation: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/search_index

   Please let us know any feedback you may have.

2. Support highlighting with autocomplete operator

   Currently, highlighting is supported only with search, term, compound, and span operators, and this is documented in the highlighting documentation. Therefore, if highlighting is used with the autocomplete operator, then it results in an error like this:

   "Highlights can not be generated. Path: "####" is not stored statically or dynamically indexed."

   This is a feature request to add support for highlighting with the autocomplete operator.

   11 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 →
   completed  ·  Elle responded

   See examples here

3. The equals operator should support date datatype

   Currently, for querying on "date" datatypes, we can only use "range" or "near" operators. The "equals" operator supports querying only "boolean" and "objectId" values, and not date values.

   If we want to do equality based matching for date datatypes, then we can leverage "range" using "gt" and "lt" to find it. However this might be sub-optimal in some cases.

   Therefore, this is a feature request for having equals operator support date datatype (in addition to boolean and objectId).

   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 →
   completed  ·  AdminAmy (Admin, MongoDB) responded

   This is available already; see documentation.

4. The equals operator should support numeric datatypes

   Currently, for querying on "number" datatypes, we can only use "range" or "near" operators. The "equals" operator supports querying only "boolean" and "objectId" values, and not numeric values.

   If we want to do equality based matching for number datatypes, then we can leverage "range" using "gt" and "lt" to find it. However this might be sub-optimal in some cases (such as when performing equality match on decimals).

   Therefore, this is a feature request for having equals operator support numeric datatypes (in addition to boolean and objectId).

   48 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

   5 comments  ·  Delete…  ·  Admin →
   completed  ·  Elle responded

   Documentation can be found here

5. Allow autocomplete to work with email addresses.

   At the moment, an autocomplete index does not tokenize the "@" in email addresses. So when using an autocomplete search on an email address field, the search breaks as soon as the "@" is entered.

   I started a thread in the community about this very issue.

   https://developer.mongodb.com/community/forums/t/mongo-search-autocomplete-type/10561/5

   16 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 →
   completed  ·  AdminAmy (Admin, MongoDB) responded

   You can achieve this functionality by using setting the autocomplete field mapping's `analyzer` field to lucene.keyword (see example) or a custom analyzer which uses the uaxUrlEmail tokenizer. 

6. Allow $count and $sort inside $search

   Make $count and $sort directly with mongot, and dont lose time between mongot and mongodb.

   118 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

   22 comments  ·  Delete…  ·  Admin →
   completed  ·  Elle responded

   At MongoDB World last week, we announced that faster counts are now available with sharded collections. 

   
   

   We also announced a feature called Stored Source Fields which help you achieve faster post-aggregation performance. You can use this feature to experience faster sorting with Atlas Search. 

   
   

   You can read more about these two features here.

   
   

   After trying Stored Source Fields, if it does not meet your performance requirements - please vote on this new feedback item. 

7. Text Search with regex

   It would be great if Text Search allows us to query with regular expressions. E.g.

   mycoll.find({ $text: { $search: "super%"} })

   Thank you for considering my request.

   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

   completed  ·  2 comments  ·  Delete…  ·  Admin →

8. Metric for Displaying Search Index Consistency Lag

   I would like a metric that shows me what the latency is between the state of the MongoDB collection and the Search index in Atlas.

   The difference between the optime of the collection and the optime of the Search index would be the latency. Please consider exposing this metric.

   13 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 →
   completed  ·  Elle responded

   Sorry for the delay! this has been available for a while in the Atlas UI metrics tab. See all available metrics here. 

9. Add support for UUID datatypes in Atlas Search

   Currently, UUID is not one of the supported datatypes for Atlas Search. This is a feature request to add support for UUID datatypes in Atlas Search.

   52 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

   7 comments  ·  Delete…  ·  Admin →
   completed  ·  AdminAmy (Admin, MongoDB) responded

   This work is now complete. Update your search index to: 

   1. Index fields using the uuid field mapping type 

   2. Query using the equals or in operators

   3. You can also sort on UUID fields

10. Allow for specifying language-specific analyzers for the autocomplete datatype

    Currently, the autocomplete data-type doesn't allow for specifying an analyzer, which means it uses the default standard analyzer. Now, the standard analyzer divides text based on word boundaries, making it language-neutral in most cases. However, currently, another language-specific analyzer cannot be specified for autocomplete.

    This is a feature request to allow for specifying language-specific analyzers for the autocomplete data-type in the index definitions, in order to fully support autocomplete searching in languages other than English.

    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

    completed  ·  0 comments  ·  Delete…  ·  Admin →

11. Full-text search for Chinese language

    Currently to perform full-text search for Chinese text, the mongo documents need to uploaded to Solr or ES. It would be helpful if the functionality can be supported by Atlas.

    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

    1 comment  ·  Delete…  ·  Admin →
    completed  ·  Marcus Eagan responded

    We’ve added support for the Chinese Language via the Lucene CJK analyzer. You can learn more about it here: https://docs.atlas.mongodb.com/reference/atlas-search/analyzers/language/#ref-language-analyzers

12. Allow managing Atlas Search index via drivers

    Currently I need to manage my indexes via the Atlas Search API but I would like to manage them using drivers in the same way that I manage all of my other MongoDB indexes.

    34 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

    3 comments  ·  Delete…  ·  Admin →
    completed  ·  AdminAmy (Admin, MongoDB) responded

    Support is now available for:

    • NodeJS
    • C#
    • C 
    • C++
    • Java
    • PHP
    • Ruby
    • PyMongo

13. Faster Pagination

    I would like be able to paginate through search results faster.

    96 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 →
    completed  ·  AdminAmy (Admin, MongoDB) responded

    Performant sequential pagination in Atlas Search is now available on MongoDB clusters 6.0.13+ and 7.0.5+ to power Infinite Scroll, Load More, and Next/Previous Page application experiences. To specify where in your Atlas Search results to start returning results from, 1) generate Base64-encoded tokens for each document within your results using the new $meta keyword searchSequenceToken, and 2) use that token as a point of reference with the new searchBefore and searchAfter options within the $search stage. 

    
    

    For use cases not addressed by Sequential Pagination, please vote here.

14. Allow Atlas Search indexes to be restored across clusters

    Currently, when an Atlas backup snapshot from one environment is restored to another environment, it does not transfer or replicate the Atlas Search indexes from the source cluster to the destination cluster. As a result, after the snapshot is restored, the Atlas Search indexes have to be manually created on the collections in the destination cluster.

    This is a request for a functionality that will allow a snapshot-restore from one cluster to another to also replicate the Atlas Search indexes from the source cluster to the destination cluster.

    46 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

    2 comments  ·  Delete…  ·  Admin →
    completed  ·  AdminAmy (Admin, MongoDB) responded

    Atlas Search index definitions are now included in Cloud Backup snapshots of M10 or higher clusters. See Atlas Search Changelog.

15. Support HTML strip tags analyzer

    If some html text is indexed we could strip tags so searches by h1, span, div, etc... should not return results.

    For example:

    Lucene: https://lucene.apache.org/core/8_5_1/analyzers-common/org/apache/lucene/analysis/charfilter/HTMLStripCharFilter.html

    Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-htmlstrip-charfilter.html

    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 →
    completed  ·  Marcus Eagan responded

    We have added this capability as a character filter via the release of custom analyzers:

    https://docs.atlas.mongodb.com/reference/atlas-search/analyzers/custom/#htmlstrip

    Please let me know if you have any questions and enjoy!

16. Faster Faceting

    Current faceting solution is not fast enough for search use cases for larger datasets.

    38 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

    completed  ·  1 comment  ·  Delete…  ·  Admin →

17. I need to be able to search for dates and numbers in arrays

    I have sets of results which contain dates and I need to be able to search from within them. For example:

    {
      experience: [
        { name: "Abc", startDate: ISODate("2019-01-01T00:00:00.000Z"), startDate: ISODate("2020-01-01T00:00:00.000Z") },
        { name: "Xyz", startDate: ISODate("2018-01-01T00:00:00.000Z"), startDate: ISODate("2019-01-01T00:00:00.000Z") }
      ]
    }
    

    So I need to be able to do a near search across experience.startDate values, for example.

    The Date mapping documentation (https://docs.atlas.mongodb.com/reference/atlas-search/index-definitions/#date) says:

    A date cannot be indexed if it is part of an array.

    And while the number documentation doesn't mention the same restriction by experimentation I have found it has the same resriction (strings dont however). Essentially this feature request is to remove this restriction for dates and numbers.

    I have sets of results which contain dates and I need to be able to search from within them. For example:

    {
      experience: [
        { name: "Abc", startDate: ISODate("2019-01-01T00:00:00.000Z"), startDate: ISODate("2020-01-01T00:00:00.000Z") },
        { name: "Xyz", startDate: ISODate("2018-01-01T00:00:00.000Z"), startDate: ISODate("2019-01-01T00:00:00.000Z") }
      ]
    }
    

    So I need to be able to do a near search across experience.startDate values, for example.

    The Date mapping documentation (https://docs.atlas.mongodb.com/reference/atlas-search/index-definitions/#date) says:

    A date cannot be indexed if it is part of an array.

    And while the number documentation doesn't mention the same restriction by experimentation I have found it has the same resriction (strings dont… more

    25 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

    3 comments  ·  Delete…  ·  Admin →
    completed  ·  Elle responded

    Complete, view changelog for more information

18. Support M10/M20

    We'd like to use this feature but it's currently not available.

    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

    completed  ·  0 comments  ·  Delete…  ·  Admin →

19. Support Japanese Analyzer in Atlas Search

    We would like support for a Japanese analyzer in Atlas Search

    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 →
    completed  ·  Tim Frietas responded

    The CJK analyzer provides basic Japanese search capabilities—if there is a specific request for a certain type of analyzer please do create a new idea describing what is needed beyond the CJK capabilites!

20. Add boolean as a search data type

    I want to search boolean fields in my search index, but currently hit an error when trying to specify boolean fields:

    "Your index could not be built: Could not resolve type id 'boolean'"

    When is boolean type support coming?

    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 →
    completed  ·  AdminDoug (Director of Engineering, Atlas Search, MongoDB) responded

    This feature has been implemented.

    Index Definition
    https://docs.atlas.mongodb.com/reference/atlas-search/index-definitions/#boolean

    Query Operator
    https://docs.atlas.mongodb.com/reference/atlas-search/equals/