Skip to content
Studio 3T - The professional GUI, IDE and client for MongoDB
  • Tools
    • Aggregation Editor
    • IntelliShell
    • Visual Query Builder
    • Export Wizard
    • Import Wizard
    • Query Code
    • SQL Query
    • Connect
    • Schema Explorer
    • Compare
    • SQL ⇔ MongoDB Migration
    • Data Masking
    • Task Scheduler
    • Reschema
    • More Tools and Features
  • Solutions
  • Resources
    • Knowledge Base
    • MongoDB Tutorials & Courses
    • Tool/Feature Documentation
    • Blog
    • Community
    • Testimonials
    • Whitepapers
    • Reports
  • Contact us
    • Contact
    • Sales Support
    • Feedback and Support
    • Careers
    • About Us
  • Store
    • Buy Now
    • Preferred Resellers
    • Team Pricing
  • Download
  • My 3T
search

Academy 3T

  • Explore our courses
    • MongoDB 101: Getting Started
    • MongoDB 201: Querying MongoDB Data
    • MongoDB 301: Aggregation
  • Get certified

Exercise 1: Importing an aggregate statement into the Aggregation Editor

MongoDB 301: Aggregation Introducing the Aggregation Editor Exercise 1: Importing an aggregate statement into the Aggregation Editor

In this exercise, you’ll import the states_transactions.js file into the Aggregation Editor. The file contains the aggregate statement that you built in the first section of this course. You’ll use this statement as the foundation for all four exercises in this section, modifying the statement as you work through the last three exercises.

The exercises in this section are based on the sales database and the customers collection. The first section in this course demonstrated how to create the database and import the collection. Refer to that section for details on how to set them up if you haven’t done so already. In the first section, you should have also built an aggregate statement and saved it to the states_transactions.js file. If you did not, you can still complete these exercises. Step 4 in this exercise provides a work-around for importing the statement. However, you will still need to ensure that you’ve set up the customers collection.

To import an aggregate statement into the Aggregation Editor

  1. Launch Studio 3T and connect to MongoDB Atlas.
  2. In the Connection Tree, expand the sales database node and, if necessary, expand the Collections node. 
  3. Right-click the customers collection node, and then click Open Aggregation Editor. Studio 3T adds the Aggregation tab to the main window. The tab displays the Aggregation Editor, with the editor’s Pipeline tab active. At this point, the aggregation pipeline is empty.
  4. On the Aggregation Editor toolbar, click the Open button (folder icon) on the left side, navigate to the folder that contains the states_transactions.js file, and double-click the file. Studio 3T uses the aggregate statement in that file to automatically populate the pipeline, as shown in the following figure.

If you did not generate the states_transactions.js file in the first section, you can instead use the clipboard feature in the Aggregation Editor to import the statement. To do so, copy the following aggregate statement to your clipboard and then paste it into the Aggregation Editor by clicking the Clipboard button at the right end of the Aggregation Editor toolbar:

db.customers.aggregate(
  [
    { "$match": { "dob": { "$lt": ISODate("1970-01-01T00:00:00.000Z") } } },
    { "$group": 
      { "_id": "$address.state", "total": { "$sum": "$transactions" } } },
    { "$sort": { "total": -1 } }
  ],
  {
    "allowDiskUse": true,
    "collation": { "locale": "en_US" }
  }
);

Regardless of which approach you take to importing the statement, the Pipeline tab will list the aggregate statement’s three stages. Each stage listing includes the stage’s operator and its expression:

  • The first stage is based on the $match operator, which filters out all documents except those with a dob value prior to 1970.
  • The second stage is based on the $group operator, which groups data by the address.state field and finds the total number of transactions for each state.
  • The third stage is based on the $sort operator, which orders the data by the total field, in descending order.
  1. Go to the tab for the first stage. Because this stage is based on the $match operator, the tab is named 1: $match. The tab also shows the stage’s operator in the Operator drop-down list, and it provides an editor window (text box) for working with the operator’s expression.
  2. In the Stage Input pane near the bottom of the tab, click the Execute button (green right arrow). Studio 3T executes the pipeline up to but not including the current stage. This allows you to see what data is being inputted into this stage before it’s applied to the pipeline. In this case, the current stage is the first stage, so the input data includes all documents in the collection.
  3. In the Stage Output pane, click the Execute button. Studio 3T executes the pipeline up to and including the current stage, which filters the data based on the dob field. The following figure shows the results in both panes. The initial pipeline input includes 1,000 documents, but the pipeline output for this stage includes only 406 documents.

The Stage Input and Stage Output panes let you compare data before a stage runs and after it runs, making it easier to build and troubleshoot each stage within the aggregation pipeline, without impacting the other stages.

  1. Repeat steps 6 and 7 for the $group stage and $sort stage, noting how the input and output result sets compare.
  2. Go to the Query Code tab and review the aggregate statement, as shown in the following figure.

Notice that the statement includes the three pipeline stages and two statement options: allowDiskUse and collation. The options were specified as part of the original aggregate statement that you imported into the Aggregation Editor. For information about the options, refer to the first section in this course.

  1. Go to the Options tab, which is shown in the following figure.

The options that were specified in the original aggregate statement are reflected here as well. The Allow disk use option is selected, and the collation is set to en_US.

  1. Go to the Pipeline tab and click the Execute button on the Aggregation Editor toolbar. Studio 3T runs the statement and returns the results to the Pipeline output pane at the bottom of the tab, as shown in the following figure.

As expected, the pipeline groups the data by state and returns the total number of transactions per state. The data is sorted in descending order based on the values in the total field. These are the same results you’d receive if you ran the aggregate statement in IntelliShell.

  1. Leave the Aggregation tab open and the existing statement in place for the next exercise. You’ll be building on this statement by adding a new pipeline stage.

Previous Lesson
Back to Lesson
Next Topic
  • Course Home Expand All
    Building a Basic Aggregation
    4 Topics | 1 Quiz
    Exercise 1: Filtering the documents in the aggregation pipeline
    Exercise 2: Grouping the documents in the aggregation pipeline
    Exercise 3: Sorting the documents in the aggregation pipeline
    Exercise 4: Adding processing options to the aggregation
    Building a Basic Aggregation: Test your skills
    Introducing the Aggregation Editor
    4 Topics | 1 Quiz
    Exercise 1: Importing an aggregate statement into the Aggregation Editor
    Exercise 2: Replace a field in the aggregation pipeline
    Exercise 3: Reorder the fields in the aggregation pipeline
    Exercise 4: Changing the sort order in the aggregation pipeline
    Introducing the Aggregation Editor: Test your skills
    Working with Arrays in the Aggregation Pipeline
    5 Topics | 1 Quiz
    Exercise 1: Using expression operators to filter input documents
    Exercise 2: Unwinding an array to create individual documents
    Exercise 3: Grouping array values and generating a document count for each group
    Exercise 4: Writing pipeline results to a new collection
    Working with Arrays in the Aggregation Pipeline: Test your skills
    MongoDB 301 Mid-Course Feedback
    Adding Lookup Data to the Aggregation Pipeline
    4 Topics | 1 Quiz
    Exercise 1: Adding lookup data to the aggregation pipeline
    Exercise 2: Converting string values in one of the lookup fields to integers
    Exercise 3: Adding a computed ratio field based on the converted lookup field
    Exercise 4: Limiting the number of returned documents
    Adding Lookup Data to the Aggregation Pipeline: Test your skills
    Working with Reschema for MongoDB
    4 Topics | 1 Quiz
    Exercise 1: Setting up a reschema unit that includes lookup data
    Exercise 2: Defining a target collection in the reschema unit
    Exercise 3: Adding and scheduling a task to create the target collection
    Exercise 4: Running an aggregate statement against the target collection
    Working with Reschema for MongoDB: Test your skills
    Reporting with Studio 3T Aggregations
    3 Topics | 1 Quiz
    Exercise 1: Creating a view based on an aggregation query
    Exercise 2: Exporting a collection as a .csv file for use by a third-party tool
    Exercise 3: Visualizing collection data in MongoDB Charts
    Reporting with Studio 3T Aggregations: Test your skills
    Course Extras
    Return to MongoDB 301: Aggregation
  • Studio 3T

    MongoDB Enterprise Certified Technology PartnerSince 2014, 3T has been helping thousands of MongoDB developers and administrators with their everyday jobs by providing the finest MongoDB tools on the market. We guarantee the best compatibility with current and legacy releases of MongoDB, continue to deliver new features with every new software release, and provide high quality support.

    Find us on FacebookFind us on TwitterFind us on YouTubeFind us on LinkedIn

    Education

    • Free MongoDB Tutorials
    • Connect to MongoDB
    • Connect to MongoDB Atlas
    • Import Data to MongoDB
    • Export MongoDB Data
    • Build Aggregation Queries
    • Query MongoDB with SQL
    • Migrate from SQL to MongoDB

    Resources

    • Feedback and Support
    • Sales Support
    • Knowledge Base
    • FAQ
    • Reports
    • White Papers
    • Testimonials
    • Discounts

    Company

    • About Us
    • Blog
    • Careers
    • Legal
    • Press
    • Privacy Policy
    • EULA

    © 2023 3T Software Labs Ltd. All rights reserved.

    • Privacy Policy
    • Cookie settings
    • Impressum

    We value your privacy

    With your consent, we and third-party providers use cookies and similar technologies on our website to analyse your use of our site for market research or advertising purposes ("analytics and marketing") and to provide you with additional functions (“functional”). This may result in the creation of pseudonymous usage profiles and the transfer of personal data to third countries, including the USA, which may have no adequate level of protection for the processing of personal data.

    By clicking “Accept all”, you consent to the storage of cookies and the processing of personal data for these purposes, including any transfers to third countries. By clicking on “Decline all”, you do not give your consent and we will only store cookies that are necessary for our website. You can customize the cookies we store on your device or change your selection at any time - thus also revoking your consent with effect for the future - under “Manage Cookies”, or “Cookie Settings” at the bottom of the page. You can find further information in our Privacy Policy.
    Accept all
    Decline all
    Manage cookies
    ✕

    Privacy Preference Center

    With your consent, we and third-party providers use cookies and similar technologies on our website to analyse your use of our site for market research or advertising purposes ("analytics and marketing") and to provide you with additional functions (“functional”). This may result in the creation of pseudonymous usage profiles and the transfer of personal data to third countries, including the USA, which may have no adequate level of protection for the processing of personal data. Please choose for which purposes you wish to give us your consent and store your preferences by clicking on “Accept selected”. You can find further information in our Privacy Policy.

    Accept all cookies

    Manage consent preferences

    Essential cookies are strictly necessary to provide an online service such as our website or a service on our website which you have requested. The website or service will not work without them.

    Performance cookies allow us to collect information such as number of visits and sources of traffic. This information is used in aggregate form to help us understand how our websites are being used, allowing us to improve both our website’s performance and your experience.

    Google Analytics

    Google Ads

    Bing Ads

    Facebook

    LinkedIn

    Quora

    Hotjar

    Reddit

    Functional cookies collect information about your preferences and choices and make using the website a lot easier and more relevant. Without these cookies, some of the site functionality may not work as intended.

    HubSpot

    Social media cookies are cookies used to share user behaviour information with a third-party social media platform. They may consequently effect how social media sites present you with information in the future.

    Accept selected