I would like to have multiple connections in a single Compass window so that I don't have to have multiple windows open when working across many deployments.

The current Aggregation Pipeline Builder is good for authoring pipelines, but not so much for running them. The final results are limited to 20 docs and not easy to view, and viewing the intermediate stage outputs can slow down performance. There should be a way to execute a pipeline and page through the complete results.

When I query documents, It would be good to be able to delete them all, instead of having to delete them one by one (very long if you have 100 docs for example)

As a user of two or more favourites, and who cycles between them both frequently, I would like the ability to double-click on the favourite connection in the sidebar so I can quickly connect to the connection. This would speed up my journey from disconnecting from one connection > clicking on the favourite for the other connection > scrolling down to click the primary "connect button" > connecting. With it I could simple double-click to connect.

Currently, there is no way to provide Client Side Field Level Encryption options inside of MongoDB Compass. We'd like to be able to provide AWS KMS details to Compass and have it decrypt read values if the user provides the correct credentials to access the Master key.

The Node driver which Compass is built on seems to be supported so having a way to provide the AWS KMS creds needed inside of Compass would be very helpful for us.

A lot of exercises from mongodb university are designed to be executed agains a cluster in mongodb atlas, but if i'm in the office behind a corporate firewall becomes impossible to connect. Could be useful if an option to connect via http proxy o socks proxy to an instance appears in compass

Allow Compass to connect via a corporate proxy

Compass users with many deployments need the ability to:

• reorder favorites, possibly based on usage patterns, as well as,


• organize favorites into folders.

These features will allow users to efficiently access important connection favorites, even when there are a large number of deployments present.

For the Compass saved "Favorites", is it possible to save the Fav specifically without the LDAP Password and the without the Client Key Password? Instead leave them blank as a favorite, so I can then enter them each time logging in?

The reason is if the MongoDb has PHI data, and if I lost my computer, a hacker could not just click to open and gain immediate access. Thank you.

With https://jira.mongodb.org/browse/COMPASS-1083, support was added for the UUID in filters and expressions, as well as the bindata type. It would be very useful to also have direct support for NUUID and LUUID identifiers in filters, so that you don't have to do manual conversion before querying such data.

An example query could be {uuid: NUUID('e6e71462-a5a6-4348-b4b5-22d4763462d1')}

The window app is soooooo slow....
it takes forever to startup... and I have a very good workstation

Plus, I upgraded now to 1.20.5 version and NONE of my connections work anymore... they ALL timeout at 30000ms :/

I will have to downgrade it

It should be possible to import a raw execution plan generated with .explain(), and have it visualized in Compass!

Why - so we as developers don't need to read the JSON manually.

This would be very usefull when debugging slow queries using the aggregation framework.

/Alex

Once clicking on the collection in the sidebar, the sample of 20 documents automatically are retrieved and displayed in the Documents tab. In some environments with large document size and network latency, MongoDB Compass UI blocks interaction until the query has timed out.

The option to prevent automatic query in Documents tab would be ideal to prevent this issue.

Sometimes larger or smaller sampling sizes (default is 1000) are desired since queries are taking too long or the sample size is not statistically useful.

Could be a part of progressive loading/sampling.