This article was published as a part of the Data Science Blogathon
“Working smart and having utilities is always a great skill to have”
Whatever we do, if we know multiple tools for various tasks that we might have to perform then it’s an extremely useful set of knowledge. For data science and machine learning, we need data and without it, both domains cannot even exist to be applied. So, definitely knowing how to store, manipulate, ingest and import data is critical for any relative field practitioner.
Today, we will look at a very powerful functionality that is available to us when working with NoSQL data in the MongoDB database. These are Aggregate Pipelines. Such pipelines have a big contribution in exercising good MLOps practices, automating the process of data manipulation, and importing the data to feed into the network with the work of the pipeline.
1. Scoping: Defining your project, target users and a plan for how you are gonna carry a project.
2. Data: Define data and establish baseline, label and organize data, feature extraction, data validation and etc.
3. Modeling: Select and train model, perform error analysis on it.
4. Deployment: Deploy in production, monitor, and maintain the system.
So, in terms of these defined stages, the scope of the article would lie in the data category which makes the complete process of MLOps much more systematic, faster, and flexible.
Aggregation: According to formal definitions, it is a process of forming or calculating an element by the combination of several separate elements. So, in terms of MongoDB, we can add various functions on top of each other as separate elements and form a more refined and complicated function that does the job easily and with a single step.
In this article, I will show you how to use these aggregate pipelines in MongoDB compass and use these pipelines inside our python code. From my personal experience, this integration is extremely helpful. In case you don’t know about MongoDB compass and how we use it along with python, here is another article I wrote for just this purpose. Please have a look before moving further. Article Link
Let’s look at MongoDB Compass and make a simple pipeline.
In my case, I have taken an already present startup_log collection in my ‘local’ dataset in MongoDB local server. Click on startup_log to open the collection.
You can see the records in my startup_log collection. There is a total of 60 records and now we are gonna build a simple aggregate pipeline on top of it. To start click on Aggregations just beside the Documents tab below your collection name(local.startup_log).
Once you click on it, you will see such an interface, where all these left windows are where we write code for each element for aggregate, and on the right you will see the output that will be retrieved once the raw data performs the task mentioned in the window. Let us see this in action.
you can add as many stages as you want, just click the ‘ADD STAGE” button below the previous stage. The first row that you can see in the image is our complete raw data as records aligned horizontally.
Now, you can see a green button on each stage, this on-off button is used to active or inactive a certain stage in the pipeline. Really helpful for debugging if needed. A drop-down menu on the left of the button is where we will choose the functionality for each stage. Let’s see how.
Why not perform a very simple function of projection on the dataset and just extract the ‘pid’ attribute from each record.
Just to show how versatile they are, let me create another stage and create a new attribute of my own, which will have the value of the attribute (startTime) as a String (it is in Date time Format in raw data).
Once you are done with your pipelines, don’t FORGET to save the pipeline to use it later and not have to create one again and again.
Giving the pipeline a name and Saving it.
Click on the icon, mentioned in the image below, and there you will see all the saved pipelines. So just hover over the name of the pipeline you wish to use again and there you will see a button for open. See it in action.
Now time to use them with Python, but before doing that we need to copy the pipeline / or export the pipeline in a string format that is suitable for python. here is how we do it.
Click the GREEN button to copy the pipeline and be ready to use it in Python.
Again, if in case you have no idea how to use MongoDB in python, please go through this Article Link. Here is the code to do the task.
import pymongo database = pymongo.MongoClient().local.startup_log data = database.aggregate(list( <>))
you can see in the above image that the ‘database’ variable is a collection pointing to ‘startup_log’.
But even after all this, one small step is left. You see the result from the aggregate is a PyMongo Cursor which helps in iterating over the values that are retrieved from the pipeline. So to save the resultant data in a DataFrame, simply wrap the cursor with Pandas.DataFrame.
import pandas as pd dataset = pd.DataFrame(data) data.head()
Now, here you have your filtered, processed data with just a single automated pipeline. Doesn’t this feel so powerful? Well, it is for me and completely loves using them, I hope you do too.
Gargeya Sharma
B.Tech in Computer science (4th year)
Specialized in Data Science and Deep learning
Data Scientist Intern at Upswing Cognitive Hospitality Solutions
For more information, check out my GitHub Home Page.
Photo by Kaley Dykstra on Unsplash
How to Create Aggregation Pipelines in a MongoD...
How To Create An Aggregation Pipeline In MongoDB
Getting Started with MongoDB database for Data ...
Getting Mongo-ed in NoSQL manager, R & Python
A Complete Guide on Using MongoDB
Basic Introduction to Data Science Pipeline
Kafka to MongoDB: Building a Streamlined Data P...
Getting Started with Data Pipeline
MongoDB in Python Tutorial for Beginners (using...
All About Data Pipeline and Its Components
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s