[COMPASS-2989] Execute Aggregation Pipeline in Compass (not copy to shell) Created: 12/Jul/18  Updated: 10/Jan/24  Resolved: 26/Aug/21

Status: Closed
Project: Compass
Component/s: Aggregation pipeline, Embedded Shell
Affects Version/s: None
Fix Version/s: No version

Type: Story Priority: Major - P3
Reporter: Roswitha Remling (Inactive) Assignee: Claudia De Angelis
Resolution: Won't Do Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Documentation Changes: Not Needed

 Description   

Is there a reason that once a pipeline as been created and saved you need to run it in a [separate] mongo shell? Seems kind of a feature that you would on integrated in this software...

 



 Comments   
Comment by Alexandre Clément [ 01/Aug/18 ]

Exactly

Comment by Durran Jordan [ 01/Aug/18 ]

So this is solved either by 1) an embedded shell or 2) having the ability to page through the entire result set without the need to do an $out.

Comment by Alexandre Clément [ 24/Jul/18 ]

Right now the way this is explained to be done here https://docs.mongodb.com/compass/master/aggregation-pipeline-builder/  is to copy the full aggregation and run it into the mongodb shell. As you pointed out you can add a $out to save it into a collection and then read it. But really those are unnecessary steps if you simply have a shell integrated window to run the pipeline.

Comment by Durran Jordan [ 24/Jul/18 ]

I'm not sure what the exact request is here. The pipeline is executing as one builds it, and the last stages preview results are the first 20 results of the entirely executed pipeline. If you want it to execute against the entire collection then turn off sample mode. If one wants to see all results and not just the first 20, then make the last stage a $out and save them into another collection. Does this help?

Comment by Alexandre Clément [ 12/Jul/18 ]

This would be very useful +1, having to open a connection with mongo shell when you already have all the information required to run the actual query seems like a burden.

Generated at Wed Feb 07 22:31:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.