Skip to content

Atlas Search

160 results found

  1. Allow comments in JSON code

    It would be great if we could keep comments in JSON generated items such as indexes (both MongoDB and Atlas Search)

    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)
  2. Allow indexing of only part of a collection

    Would be great to be able to create an Atlas Search index that only indexes part of a collection (like partialFilterExpression for a regular index). This would be valuable in situations where a collection is quite large (which would create a lot of unnecessary overhead) but only a small fraction of it needs to be searchable.

    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)
  3. Allow retrieval of individual score from embedded document search

    When using the emeddedDocuments operator to search you get a score per document, but not per embedded document. The aggregated score is either min/max/sum/mean but what I really need is the individual score from the embedded documents in order to further filter out the best matches.

    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)
  4. Support Chinese Language Analyzer : Pinyin

    PinYin IKAnalyzer Support

    For most Chinese Speaking Customer,

    https://github.com/medcl/elasticsearch-analysis-pinyin

    Is also a popular analyzer that many of our customer is using it

    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)
  5. Pre-Compiled Synonyms Collections

    There are many instances where the synonym-related needs of users are similar. For instance, in the case of names, Robert, Rob, and Bob are considered synonymous for some use cases.

    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)
  6. atlas search null

    A string or number data type that has the value 'null' is returned and is not excluded even with filtering with query: 'null' entry. The $exists and $compound operators may benefit from excluding fields that have a value of 'null' but not exactly non-existent in a document.

    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)
  7. Allow scoring with real word frequency (instead of word frequency per shard)

    We are migrating from ES and there is an option when having a few documents to do a first query to return the term frequencies for all shards and then do the normal query using these frequencies to calculate the score.

    The option is called "?searchtype=dfsquerythenfetch" and it's documented here: https://www.elastic.co/guide/en/elasticsearch/guide/current/relevance-is-broken.html.

    It would be great to have a similar option in Atlas Search! Thank you

    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)
  8. nested facets

    in elastic we can do complex nested facet groups such as

    "aggs": {
    "resellers": {
    "nested": {
    "path": "resellers"
    },
    "aggs": {
    "min_price": {
    "min": {
    "field": "resellers.price"
    }
    }
    }
    }
    }

    It would be nice to see the same functionality in atlas search

    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)
  9. Configure Alert "Insufficient disk space to support rebuilding search indexes" via API

    Currently, it's not possible to configure the alert "Insufficient disk space to support rebuilding search indexes" via API (and therefor also not by terraform).

    When setting the respective eventTypeName "HOSTDISKSPACEINSUFFICIENTFORSEARCHINDEX_REBUILD"

    I get the following response:

    400
    request "INVALIDENUMVALUE"
    An invalid enumeration value HOSTDISKSPACEINSUFFICIENTFORSEARCHINDEX_REBUILD was specified.

    The API should support this (and any other alerts configurable by the UI).

    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)
  10. Configure Search Relevance or Results Ordering in the UI

    I want to be able to configure search relevance or the order of results with a n Atlas UI module and no code.

    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)
  11. Query_syntax operator should support lucene syntax

    At the moment the query_syntax seems to have a custom syntax. It looks similar to lucene syntax but is not the same.

    There are a few differences to azure and elastic and I don’t understand whether I am doing something wrong or not.

    What all three service have in common is that they are built on top of lucene, therefore I though that the querystring operator uses the lucene query syntax as it seems to be done by elastic and azure: https://lucene.apache.org/core/29_4/queryparsersyntax.html

    Documentation about the elastic query string query can be found under: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html

    There are a few…

    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)
  12. API to list all Atlas Search Indexes configured across all collections in the cluster

    Currently, there is an API to list all Atlas Search indexes configured for a specific collection. However, there is no API that lists all Atlas Search indexes configured across all collections across all databases, in a particular cluster. The Atlas UI shows this, but the Atlas API does not have that functionality.

    This is a feature request to add the API capability to list all Atlas Search indexes configured on all collections in a cluster.

    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)
  13. 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)
  14. Allow ability to exclude specific fields from Atlas Search

    In order to reduce index size and improve performance, we should be able to exclude specific fields from the Atlas Search index.

    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)
  15. Add truncate collection button, delete documents older than...

    In the old interface we can truncate collections without using additional software, just using WEB GUI to keep small database size.
    It would be nice to have the ability to delete older documents. This option is usable for IOT or medical implementations (Nightscout).

    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. Search Page User Interface

    We would like to have a search page that automatically hooks up our Atlas Search indexes to our application.

    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)
  17. toggle or autohide left side menu and upper menu while

    add a toggle button to minimize the width of menus taking the larger part of the screen while working with a specific cluster.

    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)
  18. Reindex from a given place in our index

    We want to be able to apply an index configuration change that we know applies only to new data we placed in our index a couple weeks ago. It appears we have to re-index the entire collection over again to apply our index config change. We'd love to just set a date and re-index for the next data just from that point in time if possible so we do not have re-index the entire collection

    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. Test plan/suite for Atlas Search

    Other search services like Elastic have public benchmarks of different data types so we can determine how they should perform: https://benchmarks.elastic.co/index.html

    Would love to see the same for Atlas Search.

    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)
  20. Allow null value in "in" operator

    Allow null value in the "in" operator. This will help reducing code to query if a document has a specific ID or null.
    Helpfull when you have documents connected to a organization and/or a project.
    So you can filter
    { in: { path: "project", value: [null, ID] }}

    Currently you have to filter this with a combination of filter, compound, should and equals with a minimumShouldMatch: 1.

    {
      compound: {
        should: [
          {
            equals: {
              path: 'project',
              value: null,
            },
          },
          {
            equals: {
              path: 'project',
              value: req.project._id,
            },
          },
        ],
          minimumShouldMatch: 1,
      },
    }
    
    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)
  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base