Compass
40 results found
-
Option to Export Multiple Collections
Add A Export Screen and the option to select the collections and also a select all option for collections inside the database
1 vote -
Command line option to delete connections
Please add a command line flag that allows deleting connections (by name or ID).
Use case:
We use SSO auth with time-limited role-based access to different deployed MongoDB Atlas environments. This is combined with a script that uses
--exportConnectionsand--importConnectionsto ensure that the user has set of connections to each environment (and level) they currently have access to. However, without a--deleteConnectionscommand, there is no way to remove connections that the user no longer has access to.1 vote -
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 😅3 votes -
Export to clipboard
When exporting query results, I would like an option to export to the clipboard in addition to the existing option to export to a file.
2 votes -
security loophole in compass
Hi Team,
In my opinion, there is a security loophole in Compass. Users are able to export data even when provided with a read-only connection string, which raises significant security concerns.
Please consider this feedback and work on improving Compass to address this issue. Users with a read-only string should not be able to export data. This enhancement would make Compass more secure and productive.
1 vote -
Make upsert or drop on import document
It would be great to be able to make what we are importing overwrite the database data, or directly perform a drop before importing. These options should be optional when importing documents.
1 vote -
Export symbols as symbols, not text
When I export documents with Symbol fields to JSON, the Symbol fields are converted to text, regardless of which of the Advanced JSON Format settings I choose. Symbol and text fields aren't the same! The JSON format should export Symbols as Symbols, e.g. "type": {"$symbol": "text"} instead of "type": "text", similar to what it does with dates and ObjectIDs.
1 vote -
Export many collections in json file.
Why i can't export many all documents of many collections in json file at the same time by select them.
5 votes -
implicit cast based on validation schema
When importing json data containing an ambiguous type (e.g. 0, which can be a double or int32) with a collection that has a validation schema1 set for a specific type (e.g. double), the server should reference the schema to resolve the type to implicitly cast the value to upon inserting the document. Otherwise, one can have a document fail validation because (in this example) the 0 was cast to an int32 instead of a double.
Thanks
1 vote -
Advanced JSON Format options need to persist.
Advanced JSON Format options need to persist, please make it a entry under settings.
It is realy anoying to deal with the setting EVERY time you export data.
In my case I use only Long dates (Unix) and I will prefer to have Relaxed always, that is FAR from the cutoff point to lose resolution on that number1 vote -
Add an option to copy a single database from one cluster to another in ATLAS
At the moment atlas doesn't have any option to copy a single database from one cluster to another.
This is very important feature when its come to developing and testing the enterprise level application.
So for my current use case we have requirement where we need to refresh selective database from prod cluster to non prod cluster to perform the load and automated regression testing over the real time data and user that we have on prod.
to handle this business use case which is very common on IT , we need a option/capability in atlas to make a selective…
1 vote -
saparator
I think for saparator exported data can be change to semicolon Thanks
1 vote -
Export database statistics
When you click on a database, you can see a listing of collections and some statistics. Add a feature to export the statistics for all collections across all databases so that data inventorying is easier.
1 vote -
1 vote
-
import export database not only one data of collection
- able to export a database with all collection and insert it also
- able to export a collection from a database and insert it to database also ,not only data of a collection but also collection self with all related
3 votes -
One more dropdown option should be there for all Columns
While Importing the files, the change of datatypes should have one more drop-down option to change all columns/field datatypes to strings/mixed/double/Int32/number, etc.
1 vote -
When exporting a collection, make sorting the fields by alphabet optional
At this moment, one can only select or deselect fields, but one cannot pick any field order other than alphanumerically sorted. I would at least expect 'collection order', but taking this even a step further, it would be awesome if the export fields could be reordered in any order.
3 votes -
Save export CSV configured fields in favourite query
In case of exporting the result of a find query in a CSV file, at the moment (v. 1.36.4) we need to select which fields we are interested at the first time and in case of reuse of the favourite query we need to select these fields again.
In fact, in the default behaviour, all fields are selected from the sampled result in the CSV exporting process.One way could be to save the selected fields from the CSV export configuration in the favourite query settings.
Other ideas?
Thanks.
1 vote -
EXPORT/IMPORT bson files
Suppport EXPORT/IMPORT bson Files.
5 votes -
10 votes
- Don't see your idea?