Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
51 results found
-
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.
25 votes -
hide index
Add a button/toggle to Hide and Unhide an Index from the Data Explorer/Indexes display for a 4.4+ deployment.
15 votes -
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 -
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 -
Allow killing operations in the RTPP without having to enable the Data Explorer
Please prioritise the decoupling of the ability to kill operations in the Real Time Performance Panel from the Data Explorer.
Currently we disable the Data Explorer on our production projects so that our developers can view the Profiler and the Metrics, without being able to query the actual data. But disabling the Data Explorer prevents us from killing operations in the Real Time Performance Panel. While reenabling the Data Explorer is an easy task, it's very easy to forget the one needs to do this in order to be able to kill operations as they do not seem related in…
7 votes -
Make Connect modal button to a location accessible from any cluster tab
I often want to connect to the cluster after browsing in the Collections tab (e.g. to run some test queries via the shell).
The Connect button (available in the Overview tab) makes connecting easy, but this button is not visible in the Collections tab -- I have to click into Overview or the Clusters page to access the Connect modal button.
Can we surface a Connect button so that it is clickable from any tab in the cluster page?
6 votes -
reactive table
Hi, i would like to ask for you to make the table view under collections when we choose a particular database to be reactive. when i press a header we want it to sort the rows from asc to desc or vise versa. thank you
5 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 -
For creating indexes, show a list of fields, so as to easily select and add field that needs indexing.
While creating indexes using MDB atlas, there is no option to select from a list the fields that we want to add for indexing. For ease of use, this functionality must be added to Atlas GUI.
4 votes -
Make collections scrollable
We have databases with many collections. The problem with that is that in order to select certain collection, I have to scroll the results part of the page. So I'm going up and down all the time I select another collection and make some query.
In sum, please add scroll in the collection explorer UI.
Regards
4 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.
4 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)
4 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…
4 votes -
Real Time data explorer
I would like to see documents inserted into the database in a shell show up on the cloud data explorer UI in real time without refreshing the screen.
3 votes -
'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 -
Copy sample results from aggregation builder
If I'm exploring a database and use the aggregation builder to quickly find some data, I'd like to be able to easily extract the results. At the moment we can't even select the result output to copy-and-paste because it activates the pipeline re-ordering view. Given there are already handles to re-order the pipeline it would be much more usable to enable select and copy in the sample query output.
2 votes -
UX Issues with Collections View in Atlas UI
UX on Collections view has some problems which are listed below;
- It takes around 10-20 seconds to load the Collections page, specifically the left panel which lists namespaces.
- Then without any user interaction or feedback, it takes another 10 seconds to focus on the top most available namespace to display details of it on right hand side panel
- Then filtering namespaces with "auth" doesn't make any change in the screen and not giving any feedback neither.
- Then inputting more letters "authen" triggers the filtering however this time it filters namespaces which had nothing to do with…2 votes -
Export results of an aggregation query to csv file
I have created an aggregation pipeline from the aggregation tab of a collection but unable to export the results of that query to a CSV file.
2 votes -
Add UI to describe collections/fields in Atlas and simple validations
Most old SQL databases allow table and column-level descriptions as a core feature. For distributed teams, or agile teams prototyping an app, it would be useful to be able to document/describe fields, expected/allowed values etc straight in the UI.
I'd like a Definitions tab after Find/Indexes in the Collections view where I can indicate BSON type and add a title/description for each field in my schema.
The JSON Schema Validation mechanism could be used as a basis for storing this information, since it already has a properties definition with a description for each field name in a document.
2 votes -
Count
Whenever a query is fed into the filter search box, ensure that the count of the result is also provided somewhere above the result of the query.
2 votes
- Don't see your idea?