Compass
35 results found
-
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 -
CRUD in recursion
i have to do some operations like delete in recursion. Any operations also may be required in recursion.
1 vote -
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 -
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 -
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 -
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 -
App Freezes on Some Aggregation Queries
When I accidentally write a $lookup pipeline query with non existing field name the application crashes. I think this bug is very annoying.
1 vote -
autosave
autosave in aggregation builder
1 vote -
Lock order or sort documents in Aggregation Pipeline Builder's preview area
When we create a pipeline, it'd help if we could check the same documents data in the different stages ( now their preview is from randomly selected documents AFAIK ), so it's inconvenient to inspect one specific documents preview phases through all the stages.
Possible solutions:
1) lock the first stage's documents' order and apply it to the following stages (if possible, eg. if the stage is $group, then we can not apply the rule to the next stage)
2) set a sorting ( if possible ) of documents. But only for the preview.1 vote -
Ability to copy paste an entire pipeline as text and split it into stages of the builder UI
The pipeline builder is powerful for constructing an aggregation pipeline. However, it would be good to copy an entire pre-written pipeline into the aggregation builder as text and have it syntactically divide the text into the aggregation builder stages UI.
This will help make pipelines written previously and not saved on Compass easily modifiable over copying each stage manually into the builder UI, which is a tedious process for long pipelines.
1 vote -
Aggregation Export Pipeline Error documentation
When I have "Builders" selected, all I get for an error is "$eq cannot be top-level". Does not help the user at all to know what this means.
1 vote -
Aggregation Pipeline builder export to R
I would like to be able to export pipelines in R syntax, as I can today in Node, Java and others. R is very picky and unforgiving about it's JSON so having it generated automatically would save a lot of time.
1 vote
- Don't see your idea?