5 results found

1. Disable the explain button while an explain is running

   The Explain Plan option does not allow ending the operation.
   When selecting the explain button, no interface animation is displayed that indicates the "running" state of the operation. Also, the tool ignores the "maxTimeMS" parameter and continues the operation even after the elapsed time.

   Steps to Reproduce

   Select the Explain Plan option > select a field to filter in the database > fill in a "maxTimeMS" value > click explain.
   Continuously clicking the explain button generates several similar operations without option to stop it.

   Expected Results

   Prevent starting multiple explain operations when there is still one in progress. Allow stop on an Explain Plan operation.
   Consider the maxTimeMS in the Explain Plan option.

   Actual Results

   Explain operations cannot be interrupted by the user and he doesn't know if something is actually being executed.

   Additional Notes
   Compass readonly version 1.35.0

   The Explain Plan option does not allow ending the operation.
   When selecting the explain button, no interface animation is displayed that indicates the "running" state of the operation. Also, the tool ignores the "maxTimeMS" parameter and continues the operation even after the elapsed time.

   Steps to Reproduce

   Select the Explain Plan option > select a field to filter in the database > fill in a "maxTimeMS" value > click explain.
   Continuously clicking the explain button generates several similar operations without option to stop it.

   Expected Results

   Prevent starting multiple explain operations when there is still one in progress. Allow stop… more

   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

   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
   started  ·  AdminMassimiliano (Admin, MongoDB) responded

   We made explain plans cancellable. The new functionality is available in the most recent beta and will be rolled out in the next GA release.

2. Provide an UI option to limit Compass to a single database connection by setting the maxPoolSize to 1 in the driver

   There are some authentication setups in the field that require customers to approve every attempt to use their external credentials (such as LDAP passwords) via manual interaction with an MFA vendor's app (a good example would be Okta Verify).

   When the driver has a connection pool greater than 1 (the current default is 10), it may spawn additional connections to the database without letting the customer know. This may result in authentication failures for the various commands - if the customer misses the MFA prompt on their device.

   The current solution is to set the maxPoolSize=1 option in the connection string, since the connection settings dialog doesn't provide such explicit option.

   The proposed fix is to introduce a new connection option, for example: "Limit Compass to a single database connection" that will set the maxPoolSize=1 option in the driver with a helpful tooltip, explaining the benefit for MFA setups described above.

   There are some authentication setups in the field that require customers to approve every attempt to use their external credentials (such as LDAP passwords) via manual interaction with an MFA vendor's app (a good example would be Okta Verify).

   When the driver has a connection pool greater than 1 (the current default is 10), it may spawn additional connections to the database without letting the customer know. This may result in authentication failures for the various commands - if the customer misses the MFA prompt on their device.

   The current solution is to set the maxPoolSize=1 option in the connection… 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

   started  ·  0 comments  ·  Connectivity  ·  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

3. Have option to make "Fill in connection fields individually" view the default upon start up

   Currently, MongoDB Compass defaults to showing the "Paste connection string" view upon startup. The full connection string is shown, meaning that if you have any saved favorites, the username and password will be immediately visible upon the screen. This seems like a security risk, especially for use in public settings.

   Additionally, if your saved favorite includes SSH tunneling settings, these settings will not be applied if you try to connect to the database from the "Paste connection string" view, leading to connection failure. You must switch to the "Fill in connection fields individually" view before hitting Connect for the SSH tunnel to be created.

   Both of these problems could be alleviated by providing an option to make the "Fill in connection fields individually" view the default, as this latter view masks the password.

   Thanks,
   -- Sam

   Currently, MongoDB Compass defaults to showing the "Paste connection string" view upon startup. The full connection string is shown, meaning that if you have any saved favorites, the username and password will be immediately visible upon the screen. This seems like a security risk, especially for use in public settings.

   Additionally, if your saved favorite includes SSH tunneling settings, these settings will not be applied if you try to connect to the database from the "Paste connection string" view, leading to connection failure. You must switch to the "Fill in connection fields individually" view before hitting Connect for the SSH… more

   •  

   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

   started  ·  4 comments  ·  Connectivity  ·  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

4. I need to scan and page through query results quickly, display more documents

   The current document display paging for query results is not sufficient when large numbers of documents match the query filter.
    
   - Add "First" and "Last" buttons to the "Displaying documents" paging controls.
   - Make the number of documents displayed per page configurable (20 is insufficient)

   27 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

   3 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
   started  ·  AdminBetsy (Admin, MongoDB) responded

   In Compass v1.43.6, we released a feature that allows users to increase the number of documents displayed up to 100 documents. I previously marked this feedback item as "Completed," but I will mark it only as "Started" now given that we haven't released the 2nd improvement mentioned in the description yet:

   • Add "First" and "Last" buttons to the "Displaying documents" paging controls.

   If there are other related improvements that you would like to see, please don't hesitate to reach out!

5. Share aggregation pipelines across clusters/namespaces and with other people

   Aggregations can be saved in Compass but they are only accessible in the Aggregation Builder for the specific cluster and namespace. It would be good to be able to reuse pipelines across different clusters and namespaces (e.g. I build it against my staging database but then I want to also test it in prod).

   It would also be great to have a way to share a library of pipelines with the rest of the team. In the ideal scenario, pipelines would be versioned and multiple people would be able to contribute to a shared library of pipelines.

   24 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

   3 comments  ·  Aggregation pipeline builder  ·  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
   started  ·  AdminMassimiliano (Admin, MongoDB) responded

   With the new My Queries screen we introduced in Compass 1.31 it's possible to see and search for all queries and aggregations in one place and if the namespace they were originally built against is not available in the current cluster, it's possible to apply them to a different namespace.

   
   

   Sharing with other people is not possible yet but from the My Queries screen it's possible to copy a pipeline in one click.