Skip to content

Atlas Search

58 results found

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

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

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

  5. 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 →
  6. Extending Range operator support to ObjectId values

    If the Range operator supports ObjectId, it'll be really useful for the application that sorts or paginates data using _id, since _id is sorted by default.

    9 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 →
  7. Wildcard Atlas Search

    We put a large amount of data inside of Atlas Search but don't always know where a field actually exists. For example we might have a field that is indexed but is several objects deep, and without knowing the path notation to that field we can't find it.

    For example instead of

    path: products.christmas.decorations.tree.ornaments
    query: globes

    It would be great if we could do something like

    path: products.*
    query: globes

    8 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 →
  8. Atlas Search Custom Analyzers

    We want the ability to create our own custom analyzers in Atlas Search. It seems like the option might be there as there is a Define Analyzers button but it is not documented and the syntax does not match what I would expect to be valid, resulting in an index that never finishes building.

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

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

    1 comment  ·  Admin →
  11. Atlas Search Query Profiler/Explainer

    Similar to How in MonogDB you can perfrom db.collection.find().explain() or how in Elastic you have the Explain API (https://www.elastic.co/guide/en/elasticsearch/reference/current/search-explain.html)

    It would be great to know how scores are arrived at in Atlas Search.

    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

  12. Function scores for Search

    Elastic allows you to do to function scores, which allow us flexibility in manipulating results during certain queries. is this coming to Atlas Search?

    https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html

    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

    1 comment  ·  Admin →
    completed  ·  Marcus Eagan responded

    We now support a variety of function scores including constant, arithmetic, gaussian, path, score, and unary operators.

  13. Allow aggregate pipeline on input documents before Atlas Search indexing

    If Altas Search allowed us to apply an aggregate pipeline to input documents before they are sent to Atlas Search for indexing, it would open up a TON of new possibilities not currently supported. We could do data transformations, type conversions, synthetic fields, etc.. I've opened up a number of other suggestions for these things, but an input aggregate pipeline could solve all of them in one "easy" solution. Since aggregate pipelines already exist and are deeply embedded in MongoDB, I'm hoping it would be trivial to implement as well. Simply pick up one or more new documents to be…

    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

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

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

    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

  16. Soundex/phonetic filter support

    We need support for Soundex or phonetic filters for our use cases so we can support searches for similar sounding terms. thank you!

    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

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

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

    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. Full Text Index over a view

    My organization has a few use cases where we have a service 'join' various docs and write them into a 'consolidated doc' in elastic search to support various nested query requirements. It would be great if we could use FTS on a mongo/atlas view as we could then eliminate the need for our data joining service and its associated latency and consistency issues.

    Also fyi - it appears this is 'possible' in the current Atlas portal/UI and via the API. You can define a full text index on a view - but it disappears after a minute or two.

    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

  20. Add $search to aggregation pipeline builder in Atlas

    Right now I can write shell queries and Compass queries that can leverage $search in the aggregation pipeline, but not in Atlas.

    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

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

Atlas Search

Categories

Feedback and Knowledge Base