Compass
35 results found
-
Enable us to see values of expressions in aggregation pipelines
I've got a pipeline that often does a lot of collecting and combining values. What I get out of it is wrong but I have no way of knowing which part is broken since I can't see the values its collecting and the results of its maths until the final outcome.
Could you add some sort of value reading to the aggregation pipeline builder?
1 vote -
Remember "Expand all fields" output option between pages
When viewing documents returned by the aggregation pipeline, selecting the Output option of "Expand all fields" works for the page you are currently viewing, but changing pages means you need to click "Expand all fields" again for each page.
It would be good if Compass remembered that "Expand all fields" was active, and kept this on for all pages in the results.
1 vote -
Export or save in the acount the saved aggregations.
Just a simple way to save the aggregations.
2 votes -
CRUD in recursion
i have to do some operations like delete in recursion. Any operations also may be required in recursion.
1 vote -
Aggregation pipelines history for recently used aggregations.
Aggregation pipelines that have been used recently should also be saved similar to how search queries are stored.
2 votes -
A bug in aggregation's Wizard $lookup : It is not showing the accurate values for local & foreign fields.
A bug in aggregation's Wizard $lookup as it is not showing the accurate values for local & foreign fields. See the attached image
db.orders.insertMany([
{ "id" : 1, "item" : "almonds", "price" : 12, "quantity" : 2 },
{ "id" : 2, "item" : "pecans", "price" : 20, "quantity" : 1 },
{ "_id" : 3 }
])db.inventory.insertMany([
{ "id" : 1, "sku" : "almonds", "description": "product 1", "instock" : 120 },
{ "id" : 2, "sku" : "bread", "description": "product 2", "instock" : 80 },
{ "id" : 3, "sku" : "cashews", "description":…1 vote -
Array Function
Just like Javascript array functions such as filter, map having some option in drag and drop wizard with match and project stage will be more useful.
1 vote -
Aggregation Pipeline builder, allow hints
Allow setting hint to enable index debugging and optimizations
4 votes -
1 vote
-
Add the possibility to export a pipeline to java using Spring Data MongoDB
Spring Data for mongoDB support aggregation for use with their MongoTemplate, and it is less verbose and more readable than an aggregation to use with MongoClient.
It would be nice to be able to export a pipeline to Java language for this framework. Maybe an additional check box on the export popup.
Also, if checked, maybe replace the "Include Driver Syntax" checkbox by a "Include Spring Template syntax"
1 vote -
Changestream support!
On each collection, right next to the aggregation tab (or inside aggregation tab), just add a tab for changestream! And similar to the aggregation tab, where u can see all the previews for each aggregation step, users should be able to do same based on the oplogs.
2 votes -
Add Ai to stage wizard
currently stage wizard has built in suggestions, maybe if it becomes integrated with AI would become much more amazing
3 votes -
Aggregation pipeline stage labels
We would like the ability to input custom labels on aggregation pipeline stages. This would allow us to categorize or add more top/app-level context to each stage.
A draft of the implementation is in the attached uploaded image, where you can click to add label on the title bar of each stage card, with ability to view the label onHover of each stage of the execution bar.
2 votes -
Avoid running queries on an ongoing condition writing. (match, lookup...)
when performing a match, lookup or other similar ops, Don't run the query as I write the conditions but only when I'm done. this will improve speed significantly and will prevent crashes due to lack of memory on very large sets.
when an operation that filters data occurs, you can add a small toggle btn when I'm done writing the query, and only then perform the search.
another idea is to add a boolean field named done which on init will be set to false, and when a user is done writing the query it sets it last to true.…2 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.
2 votes -
more aggregation pipelines are needed and most of the time if we reach above 30 pipeline its gets struck , and more hard to use
more aggregation pipelines are needed and most of the time if we reach above 30 pipeline its gets struck , and more hard to use
1 vote -
Autogenerated random values in numbers based on ObjectId
Hi,
This is the basic suggestion from my side.we have a unique "_id" in each document while inserting the data can we make any changes in your code for example in our company we have one scenario while working on the aggregation query they need auto-generated value in numbers so it is not possible in the MongoDB.
so I thought we can do that thing based on the _id. because we have a unique field then i converted the _id to string and separated the numbers and alphabetic separately but we don't have unique values the after separating the numbers from the objectId.
can…
6 votes -
cross cluster lookup (kind of)
Hi,
This is more of an add-on request for the aggregate().Lets say we have two clusters , second clusters is derived from first cluster ( i-e some of the object ids in second cluster exist only in first cluster ).
Now I want to do a lookup for the id in the first cluster from the second cluster , which is not possible.
So , can we have another optional parameter in the aggregate function which allows us to pass the documents , over which we can apply the required stages ( i-e after using find() on cluster 2…
1 vote -
Indentation/newlines for Aggregation: Export to Language/PHP
I tried to use the the aggregation pipeline feature Export to Language, for PHP. The pipeline was quite complex, so I was surprised when I copied it into PHP Storm that the entire pipeline was on a single line, making it quite hard to read. PHP Storm will not add newlines for you when you request Code Reformatting, so the only way to make it readable was to add the newlines manually before reformatting, which is time confusing and error prone.
IMO it would be preferable if the pipeline was exported with appropriate use of newlines and indentation.
1 vote -
aggregation pipeline verification before deleting
When opening a saved pipeline - the "open" button is adjacent to the bin (cancel) button and clicking on the bin deletes the pipeline without a chance to regret.
3 votes
- Don't see your idea?