Skip to content

Atlas Search

← MongoDB Feedback Engine

Tell us how to improve Atlas Search!

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

51 results found

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

    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)
    Close
    Close

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    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)
    Close
    Close

  3. Atlas Search index creation/validation improvements

    Right now the tooltips that show errors during the search index are small and uninformative and don't really tell me what part of my index definition is wrong. I am spending a lot of time in the docs trying to find where my index structure is wrong. I'd like better error messages or more on-page guidance on how to structure things like custom analyzers.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    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)
    Close
    Close

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

    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)
    Close
    Close

  5. 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)
    Close
    Close

    We’ll send you updates on this idea

    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)
    Close
    Close

  6. 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)
    Close
    Close

    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)
    Close
    Close

  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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    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)
    Close
    Close

  8. Support Japanese Analyzer in Atlas Search

    We would like support for a Japanese analyzer in Atlas Search

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    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)
    Close
    Close
    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!

  9. Date proximity search

    We are building a ticket brokering system and showing the best events closest to a customers desired date is essential. Would love to see date proximity scoring.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    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)
    Close
    Close

  10. Add support for GeoJSON data

    We are looking to build a directory for patients to find doctors, but it appears that Atlas Search does not yet support geographical data relevance. Any chance this is coming soon?

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    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)
    Close
    Close

  11. Allow ability to create autocomplete indexes

    I want to be able to create an autocomplete index so that I do not have to build one for my typeahead search to work.

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    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)
    Close
    Close
1 3 Next →
  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base

(thinking…)