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.

158 results found

  1. Allow the ability to test Atlas Search locally

    We need text search to "somehow" work locally and ci.

    We've a multiregional team and development has to continue if there are internet problems in one of our offices.

    Our workflow consists of :

    • unitTest using in-memory-mongodb

    • local testing, using the developers local mongo instance

    • test env testing with a QA team (using atlas, but <30m)

    • production launch

    With the current feature set, the first time we can test a feature is on production. Even if low-tier availability was there the other two issues are blockers as we won't just ditch TDD for textSearch.

    367 votes
    37 comments  ·  Admin →
    How important is this to you?

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

    91 votes
    9 comments  ·  Admin →
    How important is this to you?

  3. Support for nested datatype search

    It appears that Atlas Search does not yet support nested documents in arrays like MongoDB

    https://docs.mongodb.com/v4.2/reference/operator/query/elemMatch/

    41 votes
    3 comments  ·  Admin →
    How important is this to you?

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

    30 votes
    2 comments  ·  Admin →
    How important is this to you?

  5. Support Decimal128

    Enable indexing and querying of near and range operators for Decimal128.

    30 votes
    10 comments  ·  Admin →
    How important is this to you?

  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.

    27 votes
    3 comments  ·  Admin →
    How important is this to you?

  7. Atlas Search on serverless instances

    Hi,

    I'd like to use Atlas Search on Atlas Serverless.

    24 votes
    2 comments  ·  Admin →
    How important is this to you?

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

    23 votes
    3 comments  ·  Admin →
    How important is this to you?

  9. Support ObjectID as a datatype for search facets

    I'm really interested in using search facets to boost search performance, but one of the fields that I want to filter by is an ObjectId.

    I believe the only supported facet types are [date, numberFacet, stringFacet].

    21 votes
    2 comments  ·  Admin →
    How important is this to you?
    AdminAmy (Admin, MongoDB) responded

    You can now transform documents for Atlas Search, enabling you to index and query (including `facet`) ObjectID fields as a String. See how here .

  10. Hierarchical/Multi-Level filters/facets.

    As a user, I'd like to be able to compute faceted counts on multi-levels of categorization.

    20 votes
    1 comment  ·  Admin →
    How important is this to you?

  11. Support for Index Partitions

    When I reach Lucene's 2 billion document limit, I would prefer to partition my index instead of being forced to Shard my database.

    19 votes
    1 comment  ·  Admin →
    How important is this to you?

  12. Return results from within arrays

    I have a document that looks like this:
    {
    shoppingList: [ { name: "red hat"}, { name: "green shoes"} ]
    }

    I would like to query $search for "green" and return {name: "green shoes"} instead of returning the entire document.

    19 votes
    planned  ·  4 comments  ·  Admin →
    How important is this to you?

  13. 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…

    15 votes
    3 comments  ·  Admin →
    How important is this to you?
    planned  ·  Elle responded

    Admin mistake! Long Numbers are also still unavailable. Reopening this and I am sorry for the confusion. 

  14. Allow faceting on boolean fields

    Right now you can only facet on string, number, date fields.
    https://www.mongodb.com/docs/atlas/atlas-search/facet/#facet-definition

    I would like to also be able to facet on boolean fields.

    14 votes
    1 comment  ·  Admin →
    How important is this to you?
    AdminAmy (Admin, MongoDB) responded

    You can now transform documents for Atlas Search, enabling you to index and query Boolean fields as a String to support faceting. See how here.

  15. Support Collation for Atlas search sort

    I have a use case to sort by product names (strings). We have products that start with letters and some that start with numbers. Currently, the products that begin with numbers are always at the top when you sort in ascending order. We would like to sort alphanumerically so that the products beginning with letters are displayed first and those with numbers at the very end.

    It would therefore be nice if the $search operator could support collations with the sort parameter.
    See: https://www.mongodb.com/community/forums/t/atlas-search-sort-with-collation-locale/269296/5

    13 votes
    0 comments  ·  Admin →
    How important is this to you?

  16. $bucketAuto for number facets

    As a developer, I would like to have functionality for NumberFacets similar to the $bucketAuto operator, so that I can define the number of buckets I want instead of setting the boundaries myself.

    This function is helpful in situations where you don't know the boundaries or can't calculate them easily.

    Example:
    myNumberFacet: {
    type: 'number'
    path: 'path.to.my.field'
    buckets: 1000
    }

    13 votes
    1 comment  ·  Admin →
    How important is this to you?

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

    12 votes
    1 comment  ·  Admin →
    How important is this to you?

  18. Analzye Endpoint or Analysis Screen

    Please show how an index is analyzed based on a given index definition.

    12 votes
    planned  ·  2 comments  ·  Admin →
    How important is this to you?

  19. MongoT (Atlas Search) logs available

    Provide mongot logs (Atlas Search) available to the customers to be downloaded and analyzed like right now it is possible to download and analyze mongod logs (classic db).

    11 votes
    0 comments  ·  Admin →
    How important is this to you?

  20. Sorting within nested objects. Allow filters on sort operation

    Atlas search sorting currently only supports a direct sort on root level fields or nested fields indexed as type "document": https://www.mongodb.com/docs/atlas/atlas-search/sort/

    Sorting cannot be done in conjunction with a filter, so a sort operation on an array of objects sorts based on the values of every document in the array. Filtering the objects inside the array and then sorting is not supported

    OpenSearch supports sorting with filtering: https://www.elastic.co/guide/en/elasticsearch/reference/current/sort-search-results.html#nested-sorting

    Here is an example of how that is done in elastic search and it would be very useful to have an equivalent feature in Atlas Search:

    POST /_search
{
   "query": {
      "nested":
    …
    10 votes
    1 comment  ·  Admin →
    How important is this to you?
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base

(thinking…)