Skip to content

Atlas Search

51 results found

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
  2. Faster Sorting with Atlas Search

    I am looking to achieve a faster sort when using Atlas Search.

    Please comment if you tried Stored Source Fields and it did not meet the performance you were looking for.

    Stored Source Fields Docs:
    Index - https://www.mongodb.com/docs/atlas/atlas-search/stored-source-definition/
    Query - https://www.mongodb.com/docs/atlas/atlas-search/return-stored-source/

    46 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  3. Support sorting by the search relevance when custom sorting search results.

    Our search index is mostly data, so we get a lot of documents with identical search relevance. We would like to use the newly announced sort feature, but we need to retain the sort relevance (score) as the primary sort criterion. We want to additionally specify reverse chronological order as the secondary criterion. Adding the missing ability to also sort by the score would solve our need.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. case insenstive sorting in atlas search

    we need a way to get results back from an atlas search that will be case-insensitive.
    currently, we need to index many columns with an upper option just to cover this need.
    we looking for the same level of support that ELK has.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  5. Support querying with numeric arrays (like $in)

    I want to be able to query for multiple numbers in the same query without having to specify separate “range” clauses (or “equals” when they are supported with numbers).
    ie. I want to be able to query for [1, 2, 3] and any document which matches 1, 2, or 3 gets returned.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. Allow indexing and querying for null datatype in Atlas Search

    The null datatype is not amongst the datatypes that Atlas Search supports at this time. As a result, if the use-case is to perform a text search on some fields and perform an equality/inequality check on other field(s) to see if it is/isn't null, then we need to have a $match stage following the $search stage, which is detrimental to the query performance as documented here. This is an enhancement request to allow indexing and querying for null datatype in Atlas Search, to avoid the above scenario.

    47 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  7. MongoDB University Course on Atlas Search

    I'd like to see a MongoDB university course on Atlas Search

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  8. Allow autocomplete search on an array of strings

    Currently, one can't use the autocomplete type to index fields whose value is an array of strings. This is a feature request to allow autocomplete indexing and searching on an array of strings.

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. Allow $count and $sort inside $search

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

    118 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    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. 

  10. Allow autocomplete on nested document field

    Although I can index a nested field using the autocomplete type, it does not return any results when queried.

    Here's an example snippet from an index definiton:

      "Customers": {
        "dynamic": false,
        "fields": {
          "Name": {
            "foldDiacritics": true,
            "maxGrams": 8,
            "minGrams": 3,
            "type": "autocomplete"
          }
        },
        "type": "document"
      },  
    

    In the above example, for a customer named "John Smith" I'd expect to get a result for "joh" when querying on the Customer.Name path. But I currently get no results.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Admin →
  11. Allow autocomplete to work with special characters and Asia languages

    Hello,

    We are now using Atlas Search, with a deep dive in this feature, we found out that it will be very cool to support "special characters" (such as @,-) and "Asia languages (such as Chinese)" for autocomplete. I think this is a requirement for many world wide companies. We can't allow a search engine which only cover a part of our clients because our business is with people form the whole world.

    Thank you in advance,

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. Functionality that provides details of how a score was calculated for an individual document

    Every document returned by an Atlas Search query is assigned a score based on relevance. Many factors can influence a document's score, including the position of the search term in the document, the frequency of occurrence of the search term in the document, the type of operator the query uses, the type of analyzer the query uses, etc.

    We do have an explain functionality in Atlas Search, which returns information about the $search query plan and execution statistics. The results returned by explain("executionStats") has a section on score, which provides statistics related to scoring documents in the result set. However,…

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  Elle responded

    [Changelog] Added scoreDetails boolean option to retrieve a detailed breakdown of the score for each document in the query results.

  13. Search Query Analytics

    For Atlas Search, I'd like to see data about what queries are run, and how many results are returned for a given query.

    15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  15. Faster Pagination

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

    96 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    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.

  16. Allow $elemMatch inside $search

    When searching array of objects inside document, it'll be useful if we have a similar operator like $elemMatch

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  17. Add ability edit query syntax in Atlas UI

    Right now you can only test simple queries in the Search Tester. I'd like to edit the query syntax to test more complex queries without the need to connect the cluster through Mongo Shell.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  18. support for the storage and high speed search of dense vectors (i.e. word embeddings)

    One feature I would like to see in mongoDB is the support for the storage and high speed search of dense vectors (i.e. word embeddings). This feature, in combination with full text search, would bring mongoDB within parity with Elasticsearch and help us simplify our architectures for these types of solutions.

    https://www.elastic.co/blog/text-similarity-search-with-vectors-in-elasticsearch

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base