Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
54 results found
-
Add visual information to indicate if a collection is capped or not.
Right now there is no way to tell through the portal or Compass if a collection is capped or not. It would be helpful if there were some visual indicator in the Data Explorer if a collection is capped and if so what the retention parameters (bytes and max documents) are set to.
2 votes -
Save common collection filter/query
As an ex-mLab customer, I used to really enjoy having common queries on collections saved, like "find a customer", "list latest X" etc Is a dropdown with a name and the query, so when you select it you can quickly perform the search.
5 votes -
Find filter autofill list should be Collection dependant
The Clusters > Collections > Find option offers an auto-fill drop-down of previous entries, which is super helpful. However, it seems to offer suggestions from previous queries of all the Collections. This is not helpful, since Document keys tend not to overlap across Collections, so it would be even more helpful if the drop-down only listed previous queries from the selected Collection.
1 vote -
'Find' should offer a JSON mode
Under Atlas > Clusters > Collections I can select a Collection and use the 'Find' option to quickly seek and edit a Document. At the moment the UI display is like JSON, but has stripped out the brackets, which makes copying the data awkward.
Feature 1: The find display UI should offer a JSON mode, so the the Document, or parts of it can be copied in JSON format.
If I select the Edit option, the editing UI is 'intelligent', in that it forces JSON compliance via the various options. However, this makes pasting in new data impossible.
Feature 2:…
3 votes -
Field with name "_id" not editable in the Atlas Collections UI.
- Add a collection
- Add an object field
- Add a string field to that object. Call it _id.
- Enter some value Save it.
- Try to Edit by clicking on the edit button.
- Try editing the value of _id (string) field. Not happening.
1 vote -
As a Collections tab, aka Data Explorer, user I want to view, search for, create and update UUID and GUID field values
The BSON spec includes support for UUID values, also known as GUID values.
The format of UUID values are defined in rfc4122.txt. For example,
f81d4fae-7dec-11d0-a765-00a0c91e6bf6
Users would like to work with UUID/GUID values in Data Explorer as a fully supported data type, including search support in the RFC layout, ability to create new document fields of type UUID, support for UUID type _id fields and the ability to edit UUID values in existing documents.
The mongo shell documentation provides this example:
UUID("3b241101-e2bb-4255-8caf-4136c566a962")
8 votes -
Sharable Atlas URL query
Add a way to share queries on Atlas UI. We could have something like:
https://cloud.mongodb.com/v2/<id>#metrics/replicaSet/<id>/explorer/<db_name>/<collection>/find?query={"email": "..."}
(URL encoded, of course)
That would open the Atlas UI in the collections tab, auto-insert and auto-run the query. This would allow non-tech users to look at data easily.
(People using the link would have to be logged in and also have the necessary permissions to access those pages, as they normally would)
6 votes -
Make the Atlas UI copy document button available via the Project Data Access Read Only permission
Hi,
We have many developers, and it is much easier for them to use the Atlas UI vs. having to RDP to another box and use tools like MongoDB shell, or Compass. At the same time, I do not wish for them to have write access via the Atlas UI. Can I please request that the Copy document button be made available via the Project Data Access Read Only permission?
Please see the attached screen snippet, and the following support case for addtional details: https://support.mongodb.com/case/00652224
Thanks,
Don1 vote -
MongoDB to throw error when detect '.' in keys insert
Not sure if MongoDB was supposed to be unstructured even for keys. Because MongoDB currently does not support '$' and '.' in its keys, is it possible for MongoDB to throw an error if '$' or '.' are detected in keys during insert? MongoDB currently does not do that and is problematic to fix for previous large databases which have '$' or '.' in keys
1 vote -
More functionalities in Collection (Data Explorer) Tab in Atlas UI
Here are some suggested functionalities
- Import and export of bulk documents.
- Quickly filter and sort the required documents. (This is achievable in Compass but not in Atlas UI)12 votes -
undo
A Simple Undo Function.
A Bit Of Background Information
Just talked to Julia from PR. Apparently "undo" is not an available feature.
YES,
there is a backup option for higher tier customers.
But,
I am not asking for a full on log of everything. Just a simple copy of the last added or deleted document in a collection for example. In case you accidentally clicked the confirm delete button on the document, your mouse was happening to hover over, when a spider jumped down from the ceiling and landed on your mouse.
It happens.Besides the point.
That functionality is…
5 votes -
Allow to configure `maxTimeMS` for commands executed from Data Explorer
What is the problem that needs to be solved? Allow to configure
maxTimeMSfor commands executed from Data Explorer.Why is it a problem? (the pain) A) Data Explorer cannot work with views in case if the view is taking >15000 ms to be load. Data Explorer cannot work with find in case if that find operation is taking >15000 ms to be completed.
1 vote -
Atlas UI (Data Explorer): Export feature .csv/.json option for collection integrated into (JS) MongoDB Atlas Cloud
Have an Export feature WITHIN Atlas UI (Data Explorer) where user can perform (select collection and export as .csv/.json directly from the website without using Compass/data dump) option for collection integrated into (JS) MongoDB Atlas Cloud.
31 votes -
Bulk multiple delete
Especially during testing, when you create masses of bogus, invalid records, would it be nice to have a better interface for batch deletion. Having selected multiple records I should be able to delete them in one go, which is not the case currently. There are multiple way to solve it UI-wise - won't dig into details.
Also, sometimes the whole collection becomes worthless, in which case a button "Clear collection" would be a handy tool.
I understand the safety concerns for collections which are in production. Maybe we could flag project/collection as development/production - in which case some features would…
5 votes
- Don't see your idea?