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, while the aforementioned statistics information provides details on the number of invocations and the nanos elapsed, it does not exactly tell "how" the score was calculated for each document.

   This is an enhancement request for introducing such a functionality that can provide the specific details on how the score(s) are calculated for individual document(s).

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

   14 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

   4 comments  ·  Delete…  ·  Admin →
   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

   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  ·  AdminSeth (Admin, MongoDB) responded

   Dedicated search nodes have been delivered for GCP and AWS.  Azure will ship soon.

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

   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. 

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

   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  ·  AdminBenjamin (Admin, MongoDB) responded

   Atlas Vector Search is now available as a public preview in MongoDB Atlas.

   
   

   https://www.mongodb.com/docs/atlas/atlas-search/knn-beta/

   https://www.mongodb.com/docs/atlas/atlas-search/field-types/knn-vector/#std-label-bson-data-types-knn-vector

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

   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

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

   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

   This work has been completed; see changelog and documentation.

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

   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 released the Wildcard Path feature in Atlas Search. You can read about it here: https://docs.atlas.mongodb.com/reference/atlas-search/path-construction/#wildcard-field-search

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

   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

   4 comments  ·  Delete…  ·  Admin →
   completed  ·  Marcus Eagan responded

   This feature has been completed and released in the latest release of Atlas Search.

   You can read the documentation here:

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

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

   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

   You can now edit the Search Tester query to run any $search query.

10. Support ngrams and edge ngrams

    We leverage ngrams and edgengrams in Elastic. We need to have these in order to perform the same searches in Atlas Search:

    https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-ngram-tokenizer.html

    https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-edgengram-tokenizer.html

    6 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 have released this feature and you can learn about it here: https://docs.atlas.mongodb.com/reference/atlas-search/index-definitions/#bson-data-types-autocomplete

    Let me know if you have questions about the new features for nGrams and edgeGrams. :)

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

    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

    Hi all,

    The explain feature for Search has been released. There are more features for Search explain coming. You can read about:

    https://docs.atlas.mongodb.com/reference/atlas-search/explain/

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

    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 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 indexed, run them through the pipeline and then send them to the Atlas Search engine for indexing.

    Here's what that might look like:

    {
      "mappings": {
        "dynamic": false,
        "aggregate": [
          { <stage> },
          ...,
          {
            "$addFields": {
              "my-synthetic-field": <expression>
            }
          }
        ],
        "fields": {
          "my-synthetic-field": {
            "type": "string"
          }
        }
      }
    }
    

    Here are some of the other suggestions I (or others) have made that could be solved with this approach:

    https://feedback.mongodb.com/forums/924868-atlas-search/suggestions/47049898-allow-indexing-of-synthetic-fields
    https://feedback.mongodb.com/forums/924868-atlas-search/suggestions/47049757-data-type-coercion-when-document-field-type-doesn
    https://feedback.mongodb.com/forums/924868-atlas-search/suggestions/47049775-allow-sort-by-boolean-fields
    https://feedback.mongodb.com/forums/924868-atlas-search/suggestions/47049775-allow-sort-by-boolean-fields
    https://feedback.mongodb.com/forums/924868-atlas-search/suggestions/40734700-support-decimal128

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

    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

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

    This feature is now available in Public Preview. Read the docs here.

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

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

    Included in our May 26th release, see docs and changelog here

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

    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.

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

    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

    This is available: 

    https://docs.atlas.mongodb.com/atlas-search/analyzers/custom/#std-label-daitchmokotoffsoundex-tf-ref

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

    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

    Completed, view changelog for more info

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

    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/

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

    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

    See a variety of tutorials on how to achieve this here: https://www.mongodb.com/docs/atlas/atlas-search/tutorial/cross-collection-tutorials/

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

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

    This feature has been implemented on Atlas.