29 results found
Right now, if we add a facet stage into the aggregation pipeline, we have to write the rest of the aggregation query manually. Users should be able to edit the sub-pipelines within a facet stage.2 votes
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
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.
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
It would be a real boon to have the aggregation pipeline builder report errors with any degree of verbosity. Right now it just says "unknown error ocurred", and I have to move my pipeline down to the shell to get a real error message.3 votes
The intent would be to run SQL queries directly on MongoDB Compass or convert them to aggregations5 votes
In aggregation view, add the possibility to add a stage Before or After.
MongoDB Compass + Atlas7 votes
Aggregations can be saved in Compass but they are only accessible in the Aggregation Builder for the specific cluster and namespace. It would be good to be able to reuse pipelines across different clusters and namespaces (e.g. I build it against my staging database but then I want to also test it in prod).
It would also be great to have a way to share a library of pipelines with the rest of the team. In the ideal scenario, pipelines would be versioned and multiple people would be able to contribute to a shared library of pipelines.18 votes
With the new My Queries screen we introduced in Compass 1.31 it's possible to see and search for all queries and aggregations in one place and if the namespace they were originally built against is not available in the current cluster, it's possible to apply them to a different namespace.
Sharing with other people is not possible yet but from the My Queries screen it's possible to copy a pipeline in one click.
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
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?