Skip to content

Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

459 results found

  1. Transactions support for Merge operation in aggregation pipeline

    Hi Team,

    can we consider supporting the transactions when we use $merge stage in mongodb aggregation pipeline?
    https://docs.mongodb.com/manual/reference/operator/aggregation/merge/#restrictions

    We have a requirement where we need to use the merge stage in pipeline and we would like to ensure automaticity in the transaction.

    The aggregation pipeline we are building can merge multiple documents into the same collection and we would like to have either all or none by using transactions and the current merge operation cant support it.

    thank you

    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

    0 comments  ·  Other  ·  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. Unpause Cluster for X Duration

    Allow customers to specify the duration they wish the unpause the cluster before Atlas will automatically re-pause the cluster. Namely for use cases where development / testing is going to commence and customer wishes to ensure cluster is paused again to reduce Atlas spend.

    Example: QA Tester is performing Atlas testing and wishes to unpause cluster, but only for the next 10 hours

    Current Atlas Control Plane: "Pause Cluster"

    Future Atlas Control Plane: "Pause Cluster for __ minutes (or hours)"

    This is similar to how customers can create temporary database users that are only active for X number of hours.…

    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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. rolling maintenance for replicasets

    Similar to the process outlined in this doc for index builds

    https://docs.mongodb.com/manual/tutorial/build-indexes-on-replica-sets/

    It would be beneficial if the same process can be allowed in Atlas for running database maintenance processes such as dropping large databases that are no longer needed or to purge out old data using this method without impacting the primary.

    Bulk Data can be purge out easier using the rolling maintenance method for example when implementing TTL index. If prior to implementing TTL index there is a lot of data to purge out that meets the TTL index criteria, this can be done prior to creating the…

    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  ·  Other  ·  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. Add a simple log filter in the Atlas log API call

    In the Atlas log API call, add a new Request Query Parameter which allow people to set a phase or string, to avoid downloading log lines including this phase or string.

    So people don't have to download large quantity of log messages that they don't need.

    For example the the NETWORK log message between replica-set members.

    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  ·  Other  ·  Admin →
    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 for programming languages other than Javascript in Atlas Realm

    By supporting programming languages other than Javascript in Atlas Realm, we would be able to cater to a wider group of developers. There is some work in this area that we can leverage - Google's J2CL transpiler for Java, Ruby's Opal transpiler...

    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  ·  Other  ·  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. Improve handling of ROLLBACK state

    Recently we had a member of a replica set in a sharded cluster enter ROLLBACK state. We just happened to notice it in an automated email sent by Atlas about primary elections which showed one of the members in ROLLBACK state.

    Fortunately for us the writes which had been reverted were not critical and we were fine with that. However, this could have resulted in serious data loss which could have gone unnoticed until a customer reached out to us.

    The handling of a situation like this one should have been much better and more user friendly. We should have…

    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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Fix Database Access Modal Bugs

    When adding user in Database Access if you try to highlight text in lets say the username area and release the click of the selection outside of the modal, it will close it and reset the data. This is extremely annoying. And makes it hard while doing simple copy pasting since you need to start over after it closes

    Also when you Grant specific privileges for a user, it wipes the username and password you already setup.

    These simple fixes would really improve the user management worflow.

    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  ·  Other  ·  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. Access key expiration date

    We would like to have option set expiration date time while creating API access keys and also ability to check expiration options through API.

    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  ·  Other  ·  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. BI connector Schema Refresh

    Based on our recent experience with BI connector refresh , we had to bump the sample size to 15000 recently. This contributed to a longer outage on our real-time dashboard reporting. It took more than an hour for the schema refresh to complete. We are hoping in future we can add couple features to Mongo Atlas :
    1) when BI connector refresh runs it would consider documents based on the last update time in the sample, so we can bring down the volume of sample considered and reduce the down time.
    2) Enable BI connector schema refresh at a collection…

    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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Option To Disable Auto Upgrades

    Would be great if we could disable the auto upgrades/updates of clusters. I.e., stop auto upgrade of cluster running 4.4.6 to 4.4.7.

    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  ·  Other  ·  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. Preserve Oplog upon storage downgrade in Azure

    Oplog was wiped out upon storage downgrade from 128Gb -> 16Gb, even though the database size incl. oplog was less than 2-3Gb.

    Please change the downgrade procedure to NOT wipe out the oplog.

    This was tested/experienced on Azure.

    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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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  ·  Other  ·  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. Permit setting a default collation at the project level, to apply to all collections etc within the databases it contains.

    Currently the highest level that collation can be set is at collection creation, and it is inherited then for any indexes created on that collection and by commands like find() that run against it.

    But it would be nice to be able to specify a default collation at the database level, or even the Atlas Project level, to apply to all collections in all databases therein, howsoever created.

    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  ·  Other  ·  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. Atlas UI deliver on Electron app

    Deliver Atlas UI as an electron app to be like an IDE and improve developers, data engineer, data scientist experience to work on a tool like VScode, IntelliJ, etc.

    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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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  ·  Other  ·  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. Document Atlas Cluster Tier Performance Expectations

    Document approximate Atlas cluster tier performance expectations that application development teams could reference when requesting an Atlas cluster (IOPS, max connections, network performance).

    This information is currently available in the Atlas UI.

    Other cloud providers such as CloudAMQP do this: https://www.cloudamqp.com/plans.html.

    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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Using Aggregation Pipeline Builder in $facet stages

    Writing more complex $facet stages (3+) without Pipeline Builder is a pain,
    so being able to use that in that type of stage would be a huge help!
    I mean being able to swap and use Pipeline Builder to every each branches of sub-pipelines in a $facet stage

    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  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Folders/Directories For Functions, Triggers, Etc

    Allow users to create directories and subdirectories for staying organized when creating many Realm triggers and functions.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Being able to create Views from aggregation pipelines in Atlas

    In Compass we can save pipelines as Views.
    That would be great also in Atlas!
    Same for both Views and On-Demand Materialized Views.

    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  ·  Other  ·  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. 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 8 10 12 22 23
  • Don't see your idea?

Feedback and Knowledge Base