Skip to content

Atlas Search

112 results found

  1. Allow queries with $search to be covered by the Lucene indexes without loading from disk in Mongo

    If the fields to be filtered on or projected on are all in the Lucene index, it would give the best latency to be able to return the data from the Lucene index only, and not have to separately look that data up from the Mongod

    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)
  2. Official React Component for Atlas Search

    One of the reasons Algolia got so popular might be the fact that they provided instantsearch.js. The library was really easy to get started and intuitive to understand.

    I read the Atlas Search's great tutorial(1) and watched the video(2) and cloned the repo FTS_MovieSearch on GitHub. They are really insightful and helpful. Yet, if there is official React component which provides some of (not all) functionalities that instasearch.js offers, that would help Atlas Search to grow.

    (I put "React" in title, but maybe vanilla JS/TS component would be better to consider)

    I used to try setting up Atlas + Elastic…

    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)
  3. Support additional highlighting options

    Right now Atlas Search highlighting only supports text in the sentence surrounding a match, ignoring any other sentences in a field that have also been indexed.

    I would like to be able to change the default behavior to meet my needs.

    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

    under review  ·  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)
  4. 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

    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)
  5. Ability to set a "minimum should match" in a query

    I can specify a percent of terms I want to match, for instance 100% means require all terms, 66% means, only return documents that matched at least 60% of the terms. (the default is 1 term)

    Ex for 100%

    search "foo bar"

    "foo bar" "bar foo" "bar hello foo" would all return

    "foo hello" would not

    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

    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. wildcard path support for range operator

    Currently wildcard path can be constructed to 4 operator(text, phrase, wildcard and regex). Some use cases will be there to use the wildcard path for numeric which can be used by range operator

    { a : { "6578ghg" : { value : "not 55" } } }
    { a : { "9578uhg" : { value : 55 } } }

    Above 2 document if we have dynamic mapping of search index and below query cannot be used as range does not support wildcard in path:

    db.dates.aggregate([ { $search :{ index:"synonyms", compound:{filter:[{text:{query:"55",path:{wildcard:"metadata.*.value"}}},{range:{gte:55,lte:55,path:{wildcard:"metadata.*.value"}}}]}}}])
    

    Is there any plans/restriction for adding wildcard path support…

    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)
  7. Allow the option to mention the number of search results needed

    I would like to get only the top scored 1000 or 2000 records while doing the search. Currently this is 2 step process : $search and then use the $limit stage.

    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)
  8. Add Atlas Search metrics into integration with Datadog

    Problem Statement,
    Atlas Search metrics (https://docs.atlas.mongodb.com/view-atlas-search-metrics#atlas-search) are not sent to Datadog (Datadog's MongoDB Atlas integration (https://docs.datadoghq.com/integrations/mongodb_atlas/)).

    Proposal,
    Add Atlas Search metrics to Datadog integration (start sending Atlas Search metrics from Atlas to Datadog).

    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)
  9. The equals operator should support date datatype

    Currently, for querying on "date" datatypes, we can only use "range" or "near" operators. The "equals" operator supports querying only "boolean" and "objectId" values, and not date values.

    If we want to do equality based matching for date datatypes, then we can leverage "range" using "gt" and "lt" to find it. However this might be sub-optimal in some cases.

    Therefore, this is a feature request for having equals operator support date datatype (in addition to boolean and objectId).

    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)
  10. Allow search users to bring their own encryption key

    I want to use my own encryption key so I know that my search data is encrypted with credentials I manage myself

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

    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. add a setting to ignore the corpus term frequency for score calculation

    indexOption:docs omits per document frequencies, but it still uses the corpus frequency.

    it would be good to have a setting to ignore the corpus frequency as well

    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. Add storedSource parameter to atlas admin API search index create/update to use with terraform

    Right now it is impossible to create atlas search index via terraform with "storedSource" parameter. This brings a lot of inconvenience and configuration-related bugs.

    Related issue

    https://github.com/mongodb/terraform-provider-mongodbatlas/issues/871

    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 faceting for embeddedDocuments

    At the moment embeddedDocuments does not allow number or date faceting.

    (https://www.mongodb.com/docs/atlas/atlas-search/define-field-mappings/#std-label-bson-data-types-embedded-documents)

    In my opinion, this does not make the operator useful, since Faceting is now the standard for every 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)
  15. 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)
  16. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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)
  18. 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)
  19. enable $and operator for multiple words in a search term (not only $or)

    It seems a commonly needed ability to decrease the amount of results from a multi-word search query instead of expanding it, since the default operator for every word is $or. If there could be a built-in $and option it will be great. 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

    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)
  20. 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)
  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base