Atlas Search

  1. Allow autocomplete to work with special characters and Asia languages

    Hello,

    We are now using Atlas Search, with a deep dive in this feature, we found out that it will be very cool to support "special characters" (such as @,-) and "Asia languages (such as Chinese)" for autocomplete. I think this is a requirement for many world wide companies. We can't allow a search engine which only cover a part of our clients because our business is with people form the whole world.

    Thank you in advance,

    20 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

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow $count and $sort inside $search

    Make $count and $sort directly with mongot, and dont lose time between mongot and mongodb.

    73 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

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Hi all,

    We’ve started to implement a lightning fast count operator inside of the $search stage and it will come soon. Sort will come a bit later than that, but optimizations around the communication between mongot and mongod should also speed sort up quite a bit. I’ll update the group as both are released to help you stay informed. If you have any questions or want to join me to discuss the syntax let me know.

  3. Target $search queries to specific shards

    Currently, sharded $search queries are scatter-gather queries and they cannot be targeted to specific shards. This is an enhancement request to target $search queries to specific shards, and thereby make them more efficient/performant.

    13 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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Atlas search to provide the ability to query number (long/double) fields

    When querying mongo using atlas search, today it requires that the query parameter be a string. Ideally, I would like to be able to also search using numbers. Our stakeholders want the ability to type into a dropdown select field , type a number, and have it pull back a list of data.

    Today, we are using atlas search to query against a multiple set of fields, and pull back the most relevant results. It would be nice to include number fields as part of our index in order to allow those same stakeholder the ability to query by the…

    8 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

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow autocomplete search on multiple fields using a wildcard path or by specifying multiple fields in the path

    Currently, (unlike the text operator) the autocomplete operator does not accept a path which is an array of field names. Also, a wildcard path ("path": {"wildcard": "*"}) cannot be specified for an autocomplete query. Therefore, the only way to perform an autocomplete search on multiple fields is by using the compound operator.

    This is a feature request to allow autocomplete search on multiple fields by using a wildcard path or by accepting an array of multiple fields in the path.

    23 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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow to create Atlas Search index on a not existing collection

    Currently it is not possible to create an Atlas Search index on a not existing collection, this makes more complicated to automatise the index creation on new clusters (e.g. via terraform).

    Would be nice to allow the implicit collection creation when creating an Atlas Search Index.

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add ability edit query syntax in Atlas UI

    Right now you can only test simple queries in the Search Tester. I'd like to edit the query syntax to test more complex queries without the need to connect the cluster through MongoCLI.

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Search Query Analytics

    For Atlas Search, I'd like to see data about what queries are run, and how many results are returned for a given query.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  9. Automatically recreate Atlas Search indexes on a collection after the collection is dropped and recreated or overwritten

    Currently, if you use the $out aggregation stage to modify a collection with an Atlas Search index, you must delete and re-create the search index. Also, if another collection is renamed with dropTarget:true to an existing collection that already has Atlas Search indexes on it, then it is necessary to recreate the Atlas Search indexes after the collection rename completes (which involves dropping the original collection).

    This is a feature request to automatically recreate the pre-existing Atlas Search indexes on a collection after that collection is dropped and recreated (using either $out or renameCollection).

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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…

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support highlighting with autocomplete operator

    Currently, highlighting is supported only with search, term, compound, and span operators, and this is documented in the highlighting documentation. Therefore, if highlighting is used with the autocomplete operator, then it results in an error like this:

    "Highlights can not be generated. Path: "####" is not stored statically or dynamically indexed."

    This is a feature request to add support for highlighting with the autocomplete operator.

    8 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  ·  Flag idea as inappropriate…  ·  Admin →
  12. Functionality that provides details of how a score was calculated for an individual document

    Every document returned by an Atlas Search query is assigned a score based on relevance. Many factors can influence a document's score, including the position of the search term in the document, the frequency of occurrence of the search term in the document, the type of operator the query uses, the type of analyzer the query uses, etc.

    We do have an explain functionality in Atlas Search, which returns information about the $search query plan and execution statistics. The results returned by explain("executionStats") has a section on score, which provides statistics related to scoring documents in the result set. However,…

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow autocomplete search on an array of strings

    Currently, one can't use the autocomplete type to index fields whose value is an array of strings. This is a feature request to allow autocomplete indexing and searching on an array of strings.

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow indexing and querying for null datatype in Atlas Search

    The null datatype is not amongst the datatypes that Atlas Search supports at this time. As a result, if the use-case is to perform a text search on some fields and perform an equality/inequality check on other field(s) to see if it is/isn't null, then we need to have a $match stage following the $search stage, which is detrimental to the query performance as documented here. This is an enhancement request to allow indexing and querying for null datatype in Atlas Search, to avoid the above scenario.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow $match or $sort stages that follow the $search stage to use MongoDB native indexes

    Currently, if there are $match or $sort stages that follow the $search stage, then those $match and $sort stages are unable to use MongoDB's native indexes on the fields being matched/sorted.

    While the documentation recommends 1) designing your $search query so that all necessary filtering occurs in the $search stage which removes the need for a $match stage and 2) instead of using a $sort stage, using the $near operator to sort documents based on a numeric, date, or geo field, such changes are not always feasible depending on the use-case. In such instances, having a $match and …

    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  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Percolator/reverse search

    Ability to store queries that allow you to supply a document and return the queries that match it.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  19. The equals operator should support numeric datatypes

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

    If we want to do equality based matching for number datatypes, then we can leverage "range" using "gt" and "lt" to find it. However this might be sub-optimal in some cases (such as when performing equality match on decimals).

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

    13 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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow $search to be a later stage in the aggregation pipeline

    Currently $search is required to be the first stage in the aggregation pipeline. It would be more intuitive if we could use after other operators, such as $match.

    37 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

    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base