Compass
350 results found
-
Use tab to validate auto-completion
Regression in version 1.36.2: it's no longer possible to validate auto-completion using "tab" key. Only "Enter" now works
4 votes -
Have the Export Colelction feature list all collection fields by default
The current feature lists the fields from a sample of documents which may miss some fields. Although it is specified in a tooltip, this is quite counter-intuitive in a NoSQL database which is all about document diversity.
When a collection has upwards to 100+ possible fields it becomes quite tedious to figure out which ones are missing from the sample data.
I would like for MongoDB Compass to find the complete list of possible fields for a selected collection and list them all out be default.
4 votes -
copy query to shell
Copy Find or Aggregation Pipeline queries directly to embedded shell. I realize you can export the query then paste it in the shell, but a nice helper would be to click a button which tells the shell to use the current collection and pastes a well-formatted query from the Documents, Schema, or Aggregation tabs of Compass directly into the shell (without executing). At least a copy to clipboard (shell format as default) button.
4 votes -
export sorted data
When clicking export collection button, the sort option specified should be copied to "Export query with filters"
Examples:
db.holidays.find (
{Date: {eq: '2022-04-08'}
).sort ({System : 1})or even make this part editable, so we can add sort option
4 votes -
Support hint for explain
Currently is not possible to force to run explain with a certain index, it would be a nice feature to have
4 votes -
Hover over object ID should display OID date
People are migrating away from a "created at" date because it's stored in the OID. However, there's currently no way to view that. Most other tools allow you to see it when you hover over it.
4 votes -
mongosh should be its own tab at the top with output options
I hate how mongosh is at the bottom. It makes it rather hard to see the results as it involves lots of scrolling, I end up having to write a js file and using
mongoshin the terminal.
It would be good if it was it's own tab at the top and give options to view the output differently.
The best example I can give is how the robo3t does it. When the data can't be viewed as a tree or table, it just outputs it in text mode.Something like this is super handy for developers and makes it…
4 votes -
Ability to drill-down and easily export deeply nested arrays
Provide the ability to drill-down and export any MongoDB array from Compass to a csv file, no matter how deeply it is stored within a document. So, one should be able to drill-down to the given array (no matter how many levels deep) in Compass, and then click "export to csv" to export only that nested array's contents to a CSV file.
4 votes -
Schema analysis should recognize dictionaries
In a sub-document, the keys may be common across most documents in the collection, or they may contain a set of random values. For example, using hostnames as the keys in the "hosts" sub-document.
{ ... hosts: { server1a: { ... } server2a: { ... } server3a: { ... } } } { ... hosts: { server1b: { ... } server2b: { ... } server3b: { ... } } }The schema analysis should recognize the above situation to avoid creating thousands of sub-fields in the schema.
4 votes -
Support Citrix as a Compass platform
Support Citrix as a new Compass platform
4 votes -
As a developer using extended JSON strict mode queries, I need Compass to also support queries in strict mode
Compass should support extended JSON strict mode queries in queries on the Documents, Schema and Explain Plan tabs.
As an example, the error message in Compass 1.14.7 for an "$oid" query is:
unknown operator: $oid
4 votes -
Could you please make the two sides of the main interface slide?
Thank you for your guys made such great application and let us use it for free.
I have a little idea for improve the usability of mongodb compress.
It hard to figure out a collection when we have a bit longer name of collections, please kindly find the following image, when we need to open a new collection, we have to close the all opening tabs and back to the first main interface, then we can find the full name in the right side, the left side is useless at this situation.
so, Could you please make the two sides…
4 votes -
Support for distinct
Add support distinct queries in Compass.
https://docs.mongodb.com/manual/reference/method/db.collection.distinct/4 votes -
Generate jsonSchema Validation Based on Schema Analysis
Since Compass already provides a schema analysis, it would be useful if that analysis could be used generate jsonSchema. The result could be a starting point for the Validation tab or used in other tools such as https://hamidihamza.com/Angular6-json-schema-form/.
4 votes -
Edit field while projecting
When projecting certain fields of a document, the UI does not allow the user to edit the document. This is a bit counter-intuitive as editing documents that have a large amount of fields is way harder than only showing the fields (via projection) that need to be edited.
3 votes -
Add Ai to stage wizard
currently stage wizard has built in suggestions, maybe if it becomes integrated with AI would become much more amazing
3 votes -
Jump to last page
A way to jump to the last page would be much appreciated - right now it shows 20 records at once, so you might need to click a lot of times, to check the last inserted. Also because refresh makes you go back to the first page!
3 votes -
Please bring back the previous dark theme (before 1.38.0)
I updated Compass to 1.38.0 (stable) on Windows. The new dark theme is too high contrast for me and I would like to switch back to the previous dark theme. Unfortunately the themes available in this version are "Light Theme" and "Dark Theme (preview)". At this point I would rather use the Light Theme than use this modern dark theme. Please bring back the previous dark theme in addition to the modern dark theme, or give us a way to customize the theme. Thank you.
3 votes -
Expand all in JSON view should be brought back
When in JSON view, we can previously expand all properties inside a document node by using CTRL+LEFT CLICK (or ALT+LEFT CLICK, i've forgotten).
This feature was removed within the last year.
3 votes -
JSON view "find" should search collapsed text
When in JSON view, the "find" operation does not search for collapsed text. If the text existing in the document (even if not shown in current view), it should expand the document to the point of the found text.
3 votes
- Don't see your idea?