Skip to content

Compass

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

18 results found

  1. Share aggregation pipelines across clusters/namespaces and with other people

    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.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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.

  2. In aggregation view, add the possibility to add a stage Before or After

    In aggregation view, add the possibility to add a stage Before or After.

    MongoDB Compass + Atlas

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Possibility to set variables used in pipeline stages

    Hi !
    It would be really handfull to have the possibility to use variables in the pipeline stages:

    var userId = ObjectId("5f61dfadc1e8960001700da8'")
    {
    $match : {user.id : userId}
    }

    for complex queries, it would avoid having to modify the id at each stages.
    Thanks !

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Text based pipeline mode

    I know you can import the pipeline from a language but I want to completely disable GUI pipeline builder and just have a text editor. The UI is too slow and clunky, just give me a text editor to directly edit and run an aggregate.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Prompt to save pipeline in case Compass is closed accidentally

    It's a human tendency to forget to continuously save an authored pipeline while constructing it. We might create a large pipeline and forget to save it before closing MongoDB Compass.

    Similar, to other softwares please add a prompt to Compass in a situation when changes are not saved before closing it.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. SQL to Aggregation framework converter

    The intent would be to run SQL queries directly on MongoDB Compass or convert them to aggregations

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Aggregation Error Verbosity

    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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Edit facet stages

    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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Store aggregation pipeline export language

    Each time you start a new aggregation, the export language is always "Python 3"., so if you're using different language, you have to set the wanted language each and every time you change the active collection or open a new tab...

    The default selected language could be:
    - the last used language (easier but still efficient)
    - the last used language for this connection
    - the last used language for this collection
    - a language configured as "preferred language" when adding a connection as favorite
    - a language configured as "preferred language" at the app level...

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. I would like $match expression to not evaluate 15*24*60*60*1000 expression with the date, instead use the literal expression

    When translating the following aggregation code, Compass evaluates the expression with the date. I would like to have a feature where it translates the literal expression to the available language.

    Example of aggregation code:
    "date": {$gte: new Date((new Date().getTime() - (15 * 24 * 60 * 60 * 1000)))}

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. autosave

    autosave in aggregation builder

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base