Skip to content

Atlas Search

157 results found

  1. Duplicate search index

    I want to be able to easily duplicate a search index in the Atlas UI.

    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

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

    Allow scoring of individual embeddedDocument searches or allow $unwind phase before $search to enable fuzzy searching for specific embeddedDocument in array of embedded documents

    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)
  3. Filtered Indexes

    Provide capability to create filtered indexes. This would allow creating tenant-specific indexes in a multi-tenant database.

    While the current implementation does support this feature in a way, it requires manual maintenance of such indexes as there is an implicit assumption that each tenant would have the same fields.

    Our core requirement is that each tenant can have their own set of fields. Filtered indexes would help reduce the size, hence requiring fewer system resources and possibly helping the database perform better.

    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)
  4. Atlas Search vs find/match

    Atlas Search is currently quite rigid and is not as awesome as find/match.

    find/match supports a variety of operators that allow looking up documents in numerous ways and is meeting our requirements to be able to query using filters such as:
    in, nin, eq, neq, gte, lte, all, any, gt, lt, size
    These operators work with find/match for any and all data types including arrays. With arrays, find/match even does an exact match comparison which is one of our requirements.

    It would be great if we can combine the speed of Atlas Search with find/match features

    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. Support full Lucene Query Parser syntax in $search

    I’m looking to expose “power user” queries through our UI, but the queryString operator only works on string data types, and is somewhat too simplistic for this purpose.

    Obviously, accepting raw user inputs and directly building a query from it is a security risk, but using something like queryString (which I do currently) seems like a safer and/or easier option.

    I would like to see a new $search operator (perhaps "lucene" or "query") that accepts the full Lucene Query Parser Syntax.

    https://lucene.apache.org/core/2_9_4/queryparsersyntax.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)
  6. Support more complex groupings in facets

    The facet collector groups results by values or ranges in the specified faceted fields and it currently returns the count for each of those groups. However, besides counting, it would be good to have facets also support more complex groupings, such as averages.

    This is a feature request to have facets support complex groupings, and expand its capabilities beyond generating counts for various buckets.

    16 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 OR Conditions

    We need support for matching for one condition out of several. This is an important usecase for my requirements.

    e.g. $or: [{ "airlines": "United" }, { "ticket_price": { $lte: 600.00 } }]

    Thanks!

    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

    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)
  8. Provide features for array comparisons

    It would be very helpful if we can lookup documents that have certain array fields that match the provided array in the query. Exact match, Any match etc should be supported. All data types should be supported.

    e.g { text: { path: "city", query: ["New York", "Los Angeles", "Kansas"] } } should return all documents that have the city as ["New York", "Los Angeles", "Kansas"].

    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

    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)
  9. geoWithin metadata reporting searchDistance

    Using geoWithin in the $search aggregation pipeline lets me use the search indexes, but it doesn't let me see the distance. I'd love to have a distanceField or perhaps a $meta that reports searchDistance similar to the one we have for searchScore

    22 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. Faster Search Index Builds

    Today, my index build may take a long time (depending on the amount of documents being indexed) and I would like to see these be faster so I am able to develop and iterate faster.

    Please comment current build time and preferred build time.

    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

    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)
  11. 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)
  12. Allow faceting on decimal fields

    I'd like to create a facet on a Price field stored as a decimal in my MongoDB documents. However, this doesn't give me the results I expect. I'm required to set the "boundaries" property on the facet to an array of integer or double values. However, when the facets are returned, they are all thrown into the "default" bucket.

    For example, if I were to declare the facet like this:

        facets: {
          price: {
            type: "number",
            path: "ProductPrice",
            // using plain integer boundaries 0,10,20,30 also fails
            boundaries: [ 0, 5.00, 10.00, 15.00, 20.00, 25.00, 30.00 ],
            default: "other",
          },
        },
    

    9 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)
  13. 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)
  14. Support min-max computation for number and date fields, within Atlas Search

    Currently, the $min and $max aggregation operators can be used in a number of aggregation pipeline stages, in order to find min/max values for fields. It would be great if either these operators were supported within $search, or if there was a way to compute the min-max values for number and date fields within Atlas Search itself. There are certain use-cases where such a functionality can prove useful.

    For instance, we can leverage the $near operator to get sorted results, and determine the sort order of the results based on the origin. However, many times, the min-max values…

    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)
  15. 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)
  16. 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)
  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. 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)
  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.

    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)
  20. Use case driven search operators and index types

    Examples: phone numbers, addresses, websites, emails

    If this would be helpful for you, please comment the data type you are looking for

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

Atlas Search

Categories

Feedback and Knowledge Base