This article was published as a part of the Data Science Blogathon.
The ADLS Gen2 service is built upon Azure Storage as its foundation. It combines the capabilities of ADLS Gen1 with Azure Blob Storage. Azure Data Lake Storage is capable of storing large quantities of structured, semi-structured, and unstructured data in their original file formats. For example, it can store Text files, CSV files, JSON files, XML files, images, videos, etc. When the uploading of files gets completed after that we can use any technologies like Databricks, or Hadoop, to process and analyze the data as per our business needs.
Data Lake Storage Gen2 makes Azure Storage the inspiration for building enterprise knowledge lakes on Azure Cloud. it’s designed to service multiple petabytes of data while sustaining many gigabits of turnout, Data Lake Storage Gen2 helps you to simply manage huge amounts of data.
A fundamental part of Data Lake Storage Gen2 is the addition of a hierarchical namespace to Blob storage. The hierarchical namespace organizes objects/files into a hierarchy of directories for efficient data access.
In this article, we will explore Azure Data Lake Storage Gen2 (ADLS Gen2) service. We are going to create a storage account using an azure free tier subscription and use Microsoft Azure Storage Explorer to create storage containers and upload the data inside the containers from our local system.
Pre-Requisite:-
Need to have at least an Azure free tier subscription. I will use a free tier subscription to perform the below steps.
Step 1 – We will open the Azure portal (portal.azure.com). This is the home page of the Azure cloud.
Step 2 – Now we will create the storage service.
Step 2.1 – To create an Azure Storage Account, first click on the “create a resource” icon from the azure services to create your service.
Step 2.2 – Type “storage account” and select the only option “storage account” to create this service.
Step 2.3 – Now, click on “Create” button.
Step 2.4 – Provide the following information in the “Basics” tab of the “Create a storage account” page –
“Project Details” Section –
“Instance Details” Section –
Step 2.5 – Now, in advance option go to Data Lake Storage Gen2 section and here to “Enable hierarchical namespace” click on the checkbox.
Step 2.6 – Finally, click on the “Review + create” button.
Step 2.7 – Once, the message “Validation passed” is displayed, click on the “Create” button.
Step 3 – Now our service got created and now you will be redirected to the storage account deployment page. Here, click on the “Go to resource” button.
Step 4 – Finally our service gets launched and we can see all the credentials that we have defined during the creation of the ADLS Gen2 storage account.
Step 5 – Finally, we verify our storage service in Microsoft Azure Storage Explorer. It will help us to create containers, and upload data files and folders from our local systems to our storage account which we have created in Azure Cloud. Install it locally and you can access all the storage-related functionality of Azure from yo. You can download it from the storage account page or just click here.
Step 6 – Now open the Microsoft Azure Storage Explorer and connect it with your Azure account. To connect, just click on the “Plug” symbol provided on the left side of the menu options and then click on the “Subscription” section, and then it will redirect you to connect your Microsoft account. Fill in the details and your azure account will get connected with storage explorer. Now you can see your storage service name inside your storage accounts dropdown.
We have successfully created our first ADLS Gen2 storage account. Now, we will upload the data inside it using Microsoft Azure Storage Explorer. To upload the data we are going to create a folder with the name “raw”. Inside this folder, we are going to upload our data. Let’s go…
Step 1 – To create a container or folder, right-click on “Blob Containers” which are inside your storage account. Now a pop will appears and here right-click on “Create Blob Container”.
Step 2 – Type the name of your folder inside the provided box as “raw”.
Step 3 – Click on the raw folder and you will see different options, click on the “upload” option. Here you will get 2 options whether you want to upload a file or you want to upload a folder. We will upload a file to our storage folder.
Step 4 – Click to upload files option and a file upload prompt will open, there you can select the file to upload. After selecting click on the “upload button” and the file gets uploaded into the raw container. I am uploading the scraped data “CSV file” named “inshort_news_data_7.csv” to our storage. You can see the below image.
Step 5 – Now your file gets uploaded into the Azure storage. You can check the “Activities” section which will display the status of your task, and whether your task is successful or gets failed.
In this article, we have discussed important steps one needs to know while creating their first Data Lake Storage Service in Azure Cloud.
This article has covered the following topics:
I hope you liked my article on ADLS Gen2. If you have any opinions or questions, then comment down below. Connect with me on LinkedIn for further discussion.
Happy Learning!
The media shown in this article is not owned by Analytics Vidhya and is used at the Author’s discretion.
Hello 👋,
I am a Data Engineer with a proven track record of working in the information technology and services industry. I am skilled in Apache Spark, Hive, SQL, Python, Hadoop, Databricks and Cloud.
How to Use Python to Automate Google Sheets? (2...
Top 10 Data Analytics Projects with Source Codes
Connecting and Reading Data From Azure Data Lake
An Overview of Using Azure Data Lake Storage Gen2
From Blob Storage to SQL Database Using Azure D...
Introduction to Azure Databricks Notebook
20 Most Frequently Asked Azure Data Factory Int...
Building an ETL Data Pipeline Using Azure Data ...
What is Data Storage and How is it Used?
Top 10 Azure Data Services Interview Questions ...
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