Compass
479 results found
-
Should be able to export saved queries as well.
The saved queries should be exported as well.
i have saved many queries with long pipelines and complex logic which I think won`t be able to write again if somehow deleted 😅4 votes -
Expiry time value in ttl index details accordion view
indexes tab showing indexes of selected collection, would be great to know what expiry time was set for ttl indexes when expanding them. recent updates to compass are really really good btw.
4 votes -
New way to close tabs
I love being able to close tabs using middle mouse button click. Please add this.
4 votes -
Split View: Split screen into two sides to compare two tabs visually
When I have more than one tab, I would like to split the view in two and have two tabs, one on the left and one on the right to be able to compare two different documents.
VScode for example has this option (see screenshot attached)
The only way to do this now is with a new instance of compass (2nd connection)4 votes -
Linux ARM 64 builds (Apple M1)
The linux support of the apple M1 and following chips is getting better in a fast pace. Would be great if mongodb compass could be used on such a device / operating system combo.
4 votes -
Font size and light themes for the mongo shell
Rather than zooming the whole compass window,chage size of font as per preference and add light theme to mongosh(Mongo Shell)
4 votes -
Sync queries across multiple computers or installations of Compass
I work on multiple computers and I find my self missing queries that I have already created on other computers. It would be nice to have queries that are linked to a collection to be synced when using Compass on other computers. Maybe something like Github can be used as the central storage for the queries or allow users to selected popular storage options if Compass can't provide the storage natively.
4 votes -
Aggregation editor improvements
settings for the following:
- Turn off auto-pairs (some people really are not used to typing with it)
- Vim keybinds (somewhat joking, but also not)
- View full documentation within Compass.
- Currently it seems the website manual is the only place to view documentation, being able to see it within Compass would be helpful
- Quick reference for operators / expressions
- Font settings (increase, boldness, change font).Really just turning off auto-closing brackets would be great.
4 votes -
shortcut
For VIM user it will be more efficient when Compass Has VIM like key binding Shortcut...
4 votes -
add refresh button in the collection tab
when you click on a collection it open a tab right ? what if you want to refresh it
let's say you are in development stage and you want to see what's being stored and all
my idea is to add hot key like CTRL R or a refresh button it will be very usefull4 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 -
CTRL+F in results
Implement a CTRF+F function to allow "text search" in results page (like in a Browser)
example : In a collection, I use "Filter" field to search document and compass returns 15 documents. I hit CTRL+F and I can search a field name or a value and navigate between.
4 votes -
Keyboard shortcut to change DB/Collection
It would be nice to have a Cmd/Ctrl + P or Cmd/Ctrl + K shortcut like in VS Code or Slack to quickly switch to a different collection or database without having to click around as much.
4 votes -
Don't search for entire document set of a collection on a new tab by default
When I want to search for documents of a collection I select the collection on the left pane and then a new tab is opened, that shows information as seen in picture
big-collection.png.However, the problem with this default configuration is that is searches for the entire document set to display the information
Displaying documents 1-20 of 1183373. The executed query is:{code}
{
"appName": "MongoDB Compass",
"command": {
"aggregate": "progress",
"pipeline": [
{
"$match": {}
},
{
"$skip": 0
},
{
"$group": {
"id": 1,
"n": {
"$sum": 1
}
}
}
],
"hint": "id_",…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 -
The JSON Schema export should be producing a jsonschema file that can be used immediately with schema validation
It currently dumps a bunch of analysis information even though the menu item is "Share Schema as JSON". This file is useless for trying to harden or define a schema, even in non-mongodb tools (like validating documents match schema in our programs).
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
- Don't see your idea?