Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
13 results found
-
Save pipelines to run in aggregation mode
A Button to save pipeline in aggregation tab and run this saved pipelines.
7 votesDanilo – Great idea. We are reviewing it at the moment. Just curious whether you use the agg tab to do adhoc analysis or test queries which you eventually put in your app?
-
Total Document count on Filter
It's a very small feature but very useful with respect to use case, whenever someone filters on Atlas nowhere it shows the total number of result we got, till we didn't reach the last page so it's very useful if we can see the total number of records at least after filtering or it will be great if it is visible on each page.
4 votes -
atlas search null
A string or number data type that has the value 'null' is returned and is not excluded even with filtering with query: 'null' entry. The $exists and $compound operators may benefit from excluding fields that have a value of 'null' but not exactly non-existent in a document.
2 votes -
Add truncate collection button, delete documents older than...
In the old interface we can truncate collections without using additional software, just using WEB GUI to keep small database size.
It would be nice to have the ability to delete older documents. This option is usable for IOT or medical implementations (Nightscout).2 votes -
toggle or autohide left side menu and upper menu while
add a toggle button to minimize the width of menus taking the larger part of the screen while working with a specific cluster.
2 votes -
search
Allow scoring of individual embeddedDocument searches or allow $unwind phase before $search to enable fuzzy searching for specific embeddedDocument in array of embedded documents
1 vote -
Enable Atlas FTS to index an Atlas cluster logs
Atlas already provides the ability to create FTS index on the collection data, but retrieving and searching on the mongod log files information is pretty bad. Customers have to download the log files, then store them, parse and index on some other tool, that typically offers FTS capabilities. Why not just cut the time it take customers to perform all of those tasks and create that ability within Atlas itself?
1 vote -
profiler search by db
Currently, the profiler search is for namespace.collection_name. If I would like to see how all collections for a given namespace or DB are behaving it's a very tedious task and not user friendly at all.
1 vote -
Leverage atlas search indexes in find and count operations
Currently the documentation wasn't outright clear that Atlas search indexes can only be leveraged through Aggregation operation. It will be great if we can leverage them in find and count operations as well.
1 vote -
Ability to search for a cluster
As an enterprise we have many projects with many clusters in each project. Our naming convention isn't always standard so it would be helpful to be able to search for a cluster based on part of the cluster name and have the search result tell me in which project the cluster exists.
1 vote -
Run aggregation pipelines on dedicated resources
When dealing with large collections(my usecase is 2billion+) it would make sense to run these aggregation's on dedicated resources like Azure Functions(my guess is that currently the aggregation pipelines are run(and somehow throttled) on the same resources as the cluster runs.
Not sure how much are the aggregations internally tied to how the data is stored(maybe they are somehow taking advantage of that) but if its straight up pipe with filters and aggregations on top of it, this would be a huge step to allow using Mongo as Big Data Platform, since it would allow reasonable scaling of the pipeline…
1 vote -
1 vote
-
More useful query error
When you enter a query, if there is any kind of syntax error, you get dumped to a page where your only option is to return to clusters. Then you need to renavigate to your db and collection to attempt a new query.
This is really frustrating as instead of just being able to go back and correct your mistake, you must start writing the query again from scratch.
Why not put users back where they were and restore the query they were attempting so it can be easily fixed? Or better yet, check the query before you try to…
1 vote
- Don't see your idea?