Skip to content

Atlas Search

45 results found

  1. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Marcus Eagan responded

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

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Support for fuzzy search and synonyms

    it is just possible to either, use synonms, or fuzzy search. Would be great to have both options in one search query

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    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  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Support M10/M20

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

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Reverse Search using edgeGram in autocomplete searches

    For searching on the last few characters of a field's values, currently the only option available is to create a nGram or need to create a custom analyzer with regex split/capture group.

    As lucene internally has the reverse option available, can we have reverse flag provided with edgeGram to perform searches from the end?

    Use case:

    Lets suppose the field is tokenNumber and we usually search by the last 5 digits of the tokenNumber itself.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Add support for creating and editing Custom Analyzers via the Visual Editor

    The Visual Editor currently does not support creating or editing custom analyzers. This is a feature request for adding support for creating and editing Custom Analyzers via the Visual Editor.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base