11 results found

1. Add support for allowDiskUse when using the Data API

   The Data API doesn't support the allowDiskUse option, leaving no way to get around this error:

   "Failed to aggregate documents: FunctionError: (QueryExceededMemoryLimitNoDiskUseAllowed) Exceeded memory limit for $group, but didn't allow external spilling; pass allowDiskUse:true to opt in"

   11 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  ·  Data API  ·  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. REST API for sizing and pricing information

   To keep our configuration on optimized terms we need a way to keep sizing and pricing data of the configuration on our side up to date. We have to get this information automatically for example via REST API.

   This would help us to be up to date concerning
   - Tier sizing: e.g. tier, RAM, CPU, min HDD, price included HDD, max HDD
   - Pricinig: e.g. how much $ per hour / month for tier ***, with XX GB HDD and RAM, KMS encryption, backup and so on

   6 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  ·  Data API  ·  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. Allow API Access via Private Endpoint Connection

   To automate processes ATLAS Admin API is used but does only work if your cluster is not connected via Private Endpoint.

   5 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

   2 comments  ·  Data API  ·  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. WriteOnly DATA API

   Hello,

   We have a similar need as the one in ticket 44935186, but we would like a WriteOnly (no delete nor read) access to the API so a partner could push data in a collection without being able to read it

   Thx and have a nice day!

   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  ·  Data API  ·  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. API KEY - Restrict by Database

   Since Mongodb Clients cannot be used in Edge Runtimes (like Vercel, Cloudflare, etc.) the user of Data API becomes inevitable. The Data API access should have same features like user roles where we can restrict an API KEY or an ENDPOINT to have acccess to a single database or multiple database.

   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  ·  Data API  ·  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. Disable (or warn about) destructive features

   We already have Termination Protection enabled in our production cluster. That's great, but only applies to the whole cluster.

   It would be great if there was a way to enable additional finer-grained safety features in MongoDB that would apply to large-scale destructive actions taken in either Atlas or mongosh. These could be presented as additional warnings or require additional confirmation even for users with administrator rights to re-consider their life choices. I.e. "are you really REALLY sure you want to drop that collection?". These could apply to the entire project, rather than individual databases or collections.

   For example, these features are rarely if ever used in our production environment:

   • db.collection.drop()
   • db.collection.remove() or db.colletion.deleteMany(), especially if the query is empty or results in a very large number of documents
   • db.collection.dropIndex() and db.collection.dropIndexes() -- the "Require Indexes for All Queries" setting is too late to catch this
   • $out operator (and perhaps $merge as well) in aggregation pipelines.

   Of those, only $out is somewhat covered: MongoDB Atlas Data Explorer's aggregation query warns the user before executing a pipeline that ends in a $out stage. mongosh has no similar warning.

   We already have Termination Protection enabled in our production cluster. That's great, but only applies to the whole cluster.

   It would be great if there was a way to enable additional finer-grained safety features in MongoDB that would apply to large-scale destructive actions taken in either Atlas or mongosh. These could be presented as additional warnings or require additional confirmation even for users with administrator rights to re-consider their life choices. I.e. "are you really REALLY sure you want to drop that collection?". These could apply to the entire project, rather than individual databases or collections.

   For example, these features… 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  ·  Data API  ·  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. As a DBA I need to be able to create/delete a single backup policy via CLI/API

   As a DBA I need to be able to create/delete a single backup policy via CLI/API.

   For some projects, I would like to be able to create a single hourly policy.
   Currently it's impossible. Default policies are created and via API I cannot delete all the other policies one by one leaving just hourly one. I also can't delete all and add a single one.

   I would like this functionality to be available both in API and CLI.

   Currently you can only
   - delete all policies
   - update existing policy by policyId

   I need to be able to delete a single policy by id
   I need to be able to create a new policy without using policyId

   Currently in CLI only the following are available
   Available Commands:
   describe Describe a cloud backup schedule for the cluster you specify.
   update Modify the backup schedule for the specified cluster for your project.
   delete Delete all backup schedules of a cluster.

   As a DBA I need to be able to create/delete a single backup policy via CLI/API.

   For some projects, I would like to be able to create a single hourly policy.
   Currently it's impossible. Default policies are created and via API I cannot delete all the other policies one by one leaving just hourly one. I also can't delete all and add a single one.

   I would like this functionality to be available both in API and CLI.

   Currently you can only
   - delete all policies
   - update existing policy by policyId

   I need to be able to delete a… 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  ·  Data API  ·  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. EmbeddedDocuments Search multiple compound fields

   Today, it doesn't seem that a $search index on a list of object documents allows for an embeddedDocument search to match on multiple properties within the document.

   So, if I have:

   [{
   name: 'Doc 1',
   attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'number' }]
   },
   {
   name: 'Doc 1',
   attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'string' }]
   }]

   I would like to be able to write a compound query like this:

   [
   {
   $search: {
   index: "default",
   compound: {
   must: [
   {
   embeddedDocument: {
   path: "attached",
   operator: {
   compound: {
   must: [
   {
   text: {
   path: "attached.name",
   query:
   "b",
   },
   },
   {
   autocomplete: {
   path: "attached.type",
   query: "string",
   },
   },
   ],
   },
   },
   },
   },
   ],
   },
   },
   }]

   And for it to only find and return this:
   {
   name: 'Doc 1',
   attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'string' }]
   }

   Today, it doesn't seem that a $search index on a list of object documents allows for an embeddedDocument search to match on multiple properties within the document.

   So, if I have:

   [{
   name: 'Doc 1',
   attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'number' }]
   },
   {
   name: 'Doc 1',
   attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'string' }]
   }]

   I would like to be able to write a compound query like this:

   [
   {
   $search: {
   index: "default",
   compound: {
   must: [
   {
   embeddedDocument: {
   path: "attached",
   operator: {
   compound:… 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  ·  Data API  ·  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

9. Handle Duplicate data in Timeseries collection

   It would be helpful by introducing the optional add on functionality of overwriting the document if it is already exists for an insert operation based on “_id” field for only timeseries collection in upcoming releases. Because if we have huge amount of sensors then data should be blindly written into timeseries collection without querying for duplicate check (Conditional inserts will definitely impact the performance).

   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  ·  Data API  ·  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

10. grpc

    You should create a grpc API like AstraDB has already done. Grpc is the ideal way for a serverless app to connect to a database. Get both of best worlds: native driver performance plus don't need to worry about database connections.

    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  ·  Data API  ·  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. Add C# Android app support

    The C# driver wraps the DnsClient library. This does not support Android so I can't access an Atlas server from a Xamarin mobile ap on Android. Perhaps you could either use another library or create a bespoke library which includes Android DNS lookup support?

    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  ·  Data API  ·  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