166 results found

1. Add noData to $sort aggregation

   Atlas Search does have the option to change the behavior for null and missing values within a search with noData: highest or noData: lowest.
   It would be great if the $sort aggregation stage would support this as well.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Update base collection of search index without Downtime

   With the GA of Atlas search indexes on views, i wanted to update some of my existing search indexes to use views.
   Then i noticed that at the moment it is not possible to update the base collection/view of an existing search index without downtime.

   You can only create a new search index with the new base collection/view and then update your applications to use the new one.
   Or you delete the existing index and create the new one with the same name.
   An option to change the base collection in the atlas ui would be helpful in these cases.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Number of documents per Facet

   It would be nice to have a number of matched documents total per Facets when doing a $searchMeta query and not only the count within the buckets itself. We cannot add all bucket counts as documents can be in multiple buckets leading to inconsistent results.
   This idea came out of a requirement to sort facets by matched documents in total.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Support more types of Views

   Currently, Atlas Search indexes can be created on Views which contain the $addFields, $set and $match (wrapping an $expr operation) stages. Support for additional stages would allow new use cases.

   If you vote for this idea, please specify which stage you need for your use case.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Addition to search Index disk space used metrics

   It would have been great if Atlas search disk metrics shares below information as well.

   1. which field(s) inside the index taking more space
   2. what is the frequency of index fields usage.
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Persist Atlas search indexes post restart

   We have a large collection on which we have a large Atlas Search index on a Workload Isolation node. In the lower environments we pause overnight to save cost. Upon restarting, the large index has to rebuild, it was taking 10hrs and this was wiping out development time.

   In posing this question to support the response was:

   "When you pause a cluster, Atlas deletes all data from the Search Nodes. Atlas automatically rebuilds the Atlas Search indexes when you resume the Atlas cluster. While Atlas rebuilds the Atlas Search indexes, the $search and $vectorSearch pipeline stages are unavailable. You can review the Considerations for Paused Clusters here."

   So it is expected behaviour. My question is why, it makes no sense to drop an index on pause and have to build it again, can we not persist them?

   Support ticket reference : https://support.mongodb.com/case/01449917 (note there is also a poiunt about during the index rebuild none - even small Search indexes were useable)

   We have a large collection on which we have a large Atlas Search index on a Workload Isolation node. In the lower environments we pause overnight to save cost. Upon restarting, the large index has to rebuild, it was taking 10hrs and this was wiping out development time.

   In posing this question to support the response was:

   "When you pause a cluster, Atlas deletes all data from the Search Nodes. Atlas automatically rebuilds the Atlas Search indexes when you resume the Atlas cluster. While Atlas rebuilds the Atlas Search indexes, the $search and $vectorSearch pipeline stages are unavailable. You can… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Terraform import for Atlas search index

   Currently it is not possible to import existing atlas search index into Terraform. Would be nice if we can import the existing atlas search index instead of re-create it via Terraform.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Support pagination when sorting by searchScore on Search Nodes

   Using searchAfter / searchBefore on Search Nodes when sorting by searchScore can be inconsistent.

   12 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. 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": {
            "path": "parent",
            "query": {
               "bool": {
                   "must": {"range": {"parent.age": {"gte": 21}}},
                   "filter": {
                       "nested": {
                           "path": "parent.child",
                           "query": {"match": {"parent.child.name": "matt"}}
                       }
                   }
               }
            }
         }
      },
      "sort" : [
         {
            "parent.child.age" : {
               "mode" :  "min",
               "order" : "asc",
               "nested": {
                  "path": "parent",
                  "filter": {
                     "range": {"parent.age": {"gte": 21}}
                  },
                  "nested": {
                     "path": "parent.child",
                     "filter": {
                        "match": {"parent.child.name": "matt"}
                     }
                  }
               }
            }
         }
      ]
   }
   

   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":

   … more
   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Search Playground  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Per-shard scaling of search nodes

    With the (somewhat recent) functionality of "asymmetric sharding", i.e.:
    - https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/advanced-cluster-new-sharding-schema
    - https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/advanced_cluster

    we are considering an architecture where we isolate specific collections or sets of collections on specific shards.

    However we are also interested in using Atlas Search for these collections. We would like to use dedicated search nodes, but because of the above architecture, we would only need those search nodes on specific shards.

    Because of this: for cost reasons, we would like the ability to scale search nodes for a shard independently, similar to how the electable nodes can be scaled independently.

    That is, we would like to have:

    shard-0: no search nodes
    shard-1: no search nodes
    shard-2: S40
    or in the future something like:

    shard-0: S10
    shard-1: S10
    shard-2: S40

    depending on the workload on each shard.

    With the (somewhat recent) functionality of "asymmetric sharding", i.e.:
    - https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/advanced-cluster-new-sharding-schema
    - https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/advanced_cluster

    we are considering an architecture where we isolate specific collections or sets of collections on specific shards.

    However we are also interested in using Atlas Search for these collections. We would like to use dedicated search nodes, but because of the above architecture, we would only need those search nodes on specific shards.

    Because of this: for cost reasons, we would like the ability to scale search nodes for a shard independently, similar to how the electable nodes can be scaled independently.

    That is, we would like… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Driver Support for sort option in Atlas Search Pipelines

    Please add support for sort as part of Atlas search for the Java driver. The current Aggregates class doesnt have it

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Include product versions in Atlas Search release notes

    I am creating this feedback idea in customer behalf.

    Customer suggests if adding product version numbers, for Atlas Search Release Notes pages. The page currently contains release dates, which does not provide sufficient information to debug Atlas maintenance upgrade execution plans.

    Example: The release referred to 18 September 2024 Release on the main page https://www.mongodb.com/docs/atlas/atlas-search/changelog/#18-september-2024-release is related to Atlas seach (mongot) version v.1.40.4.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Allow type 'token' in embeddedDocument

    Currently, string fields in an embedded document may be indexed as type 'string' using an analyzer, e.g. lucene.keyword. It is not possible, to index a string field in an embedded document as type 'token'.

    Indexing as type 'token' is relevant for using a 'range'-operator in a query or to sort by a string field. This is would be very useful when working with sortable strings.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Support sorting on fields of matching embedded documents

    The Atlas search functionality allows matching and returning embedded documents from within array fields. However, there is currently no way to sort the results based on a field within the matching embedded documents.

    This presents problems for queries where we want deterministic sorting based on an embedded field, rather than using a score-based sort which can have inaccuracies for large values, see https://www.mongodb.com/community/forums/t/function-score-result-in-inaccurate-score/296014

    For example, consider data with an "items" array containing embedded documents, where we want to sort the results based on the "number" field within the matching embedded docs. Currently we have to assign this to the score, but scores are not ideal for large values.

    It would be much better if we could do a simple sort like: "items.number"

    The Atlas search functionality allows matching and returning embedded documents from within array fields. However, there is currently no way to sort the results based on a field within the matching embedded documents.

    This presents problems for queries where we want deterministic sorting based on an embedded field, rather than using a score-based sort which can have inaccuracies for large values, see https://www.mongodb.com/community/forums/t/function-score-result-in-inaccurate-score/296014

    For example, consider data with an "items" array containing embedded documents, where we want to sort the results based on the "number" field within the matching embedded docs. Currently we have to assign this to the score,… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Ablity for serverless should be provided

    Nothing

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Search Playground  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Implement basic aritmetic operations for the Decimal128 datatype

    Feature Request:
    Implement basic aritmetic operations (e.g. addition) for the Decimal128 datatype.

    Context:
    I am working with high precision floats in Python and I am storing my data in MongoDB. When I get a high precision float out of MongoDb, I then need to convert it to the native Python decimal datatype before I can do basic arithmetic like addition. It would be great if your Decimal128 datatype supported the same mathematical operations as Python's decmial datatype. I documented this issue and provided sample code to work around the limitations here:

    https://github.com/NadimGhaznavi/kb/wiki/Handling-Floating-Point-Math-with-Python-and-MongoDb

    Love your product, keep up the awesome work!!! :)

    Feature Request:
    Implement basic aritmetic operations (e.g. addition) for the Decimal128 datatype.

    Context:
    I am working with high precision floats in Python and I am storing my data in MongoDB. When I get a high precision float out of MongoDb, I then need to convert it to the native Python decimal datatype before I can do basic arithmetic like addition. It would be great if your Decimal128 datatype supported the same mathematical operations as Python's decmial datatype. I documented this issue and provided sample code to work around the limitations here:

    https://github.com/NadimGhaznavi/kb/wiki/Handling-Floating-Point-Math-with-Python-and-MongoDb

    Love your product, keep up the awesome work!!!… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Search Playground  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Implement basic aritmetic operations for the Decimal128 datatype

    Feature Request:
    Implement basic aritmetic operations (e.g. addition) for the Decimal128 datatype.

    Context:
    I am working with high precision floats in Python and I am storing my data in MongoDB. When I get a high precision float out of MongoDb, I then need to convert it to the native Python decimal datatype before I can do basic arithmetic like addition. It would be great if your Decimal128 datatype supported the same mathematical operations as Python's decmial datatype. I documented this issue and provided sample code to work around the limitations here:

    https://github.com/NadimGhaznavi/kb/wiki/Handling-Floating-Point-Math-with-Python-and-MongoDb

    Love your product, keep up the awesome work!!! :)

    Feature Request:
    Implement basic aritmetic operations (e.g. addition) for the Decimal128 datatype.

    Context:
    I am working with high precision floats in Python and I am storing my data in MongoDB. When I get a high precision float out of MongoDb, I then need to convert it to the native Python decimal datatype before I can do basic arithmetic like addition. It would be great if your Decimal128 datatype supported the same mathematical operations as Python's decmial datatype. I documented this issue and provided sample code to work around the limitations here:

    https://github.com/NadimGhaznavi/kb/wiki/Handling-Floating-Point-Math-with-Python-and-MongoDb

    Love your product, keep up the awesome work!!!… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Allow to configure/adjust the number of nodes within a regions in a multi-region Atlas search cluster

    Today, i enabled an isolated search node cluster with 2 nodes for one of our cluster which is an multi-region cluster with 4 nodes in N.Virginia and 1 node in Oregon. I can see that search node cluster has added 2 nodes in N.Virginia and 2 nodes in Oregon.
    We use N.Virginia as our primary region and Oregon as our secondary region mainly considering it (Oregon) only for Disaster recovery purposes, so having 2 search nodes in Oregon will not be of much use for us, and I don't see an option in the mongoDB Atlas console to configure the number of nodes I want in the corresponding regions as we are able to do for the main cluster.

    Today, i enabled an isolated search node cluster with 2 nodes for one of our cluster which is an multi-region cluster with 4 nodes in N.Virginia and 1 node in Oregon. I can see that search node cluster has added 2 nodes in N.Virginia and 2 nodes in Oregon.
    We use N.Virginia as our primary region and Oregon as our secondary region mainly considering it (Oregon) only for Disaster recovery purposes, so having 2 search nodes in Oregon will not be of much use for us, and I don't see an option in the mongoDB Atlas console to configure the… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Atlas Search for time series collections

    It would be nice if we could use atlas search on a time series collection

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating