Master Jobs, Stages, and Tasks for Data Engineering Interviews

By -
Image
Mastering Spark execution internals is a "must-have" skill for Data Engineers. Whether you are prepping for an interview or debugging a slow production pipeline, understanding how Spark breaks down your code is the key to performance tuning. Spark applications follow a strict hierarchy: Jobs > Stages > Tasks . Let’s break down exactly how this works. 1. High-Level Architecture Before we dive into the code, let’s look at the components that manage the execution: Driver: The brain. It converts your code into a Directed Acyclic Graph (DAG) and schedules tasks. DAG Scheduler: Splits the graph into Stages based on "shuffles." Task Scheduler: Sends the individual Tasks to the executors. Executors: The workers that actually run the tasks in parallel. 2. Real-World Code Walkthrough: The "Wide" Transformation Let’s analyze a common scenario: reading data, filtering, grouping, and saving. # 1. Read Data (Narrow) df = sp...
Post a Comment

Git & Git Command

By -


Git is the free and open source distributed version control system that's responsible for everything GitHub related that happens locally on your computer 

🚀 Mastering Git Basics 🚀


⭐ **ls**: List contents inside the folder
⭐ **mkdir <folder_name>**: Create a project
⭐ **cd <folder_name>**: Navigate into a folder
⭐ **git init**: Initialize a Git repository
⭐ **touch names.txt**: Create a new file
⭐ **git status**: Show directory changes
⭐ **git add .**: Add all untracked files
⭐ **git add file.txt**: Add a specific file
⭐ **git commit -m "message"**: Commit changes with a message
⭐ **vi file.txt**: Edit a file
⭐ **cat names.txt**: Display file content
⭐ **git restore --staged files.txt**: Unstage a file
⭐ **git log**: View commit history
⭐ **rm -rf names.txt**: Delete a file
⭐ **git reset <commit id>**: Restore file to a specific commit
⭐ **git stash**: Temporarily store changes
⭐ **git stash pop**: Apply stored changes
⭐ **git stash clear**: Clear stored changes
⭐ **git push**: Push changes to remote
⭐ **git branch feature**: Create a feature branch
⭐ **git checkout feature**: Switch to feature branch
⭐ **git merge feature**: Merge feature branch to main
⭐ **git clone <URL>**: Clone a repository
⭐ **git remote add upstream <URL>**: Add a remote upstream
⭐ **git fetch --all --prune**: Fetch and prune remote branches
⭐ **git pull**: Fetch and merge changes
⭐ **git reset --hard upstream/main**: Reset branch to a remote commit

⭐ **Git Rebase**:
Use `git rebase -i <1st commit id>` to squash multiple commits into one. Use "Pick" to keep a commit or "Squash" to merge it with the previous one. Example:

```
Pick commit id 1
S commit id 2
S commit id 3
S commit id 4
```

Now, all commits are merged into one commit.
Attaching the cheat sheet for more info.

Comments

Post a Comment

Popular posts from this blog

Master Jobs, Stages, and Tasks for Data Engineering Interviews

By -
Image
Mastering Spark execution internals is a "must-have" skill for Data Engineers. Whether you are prepping for an interview or debugging a slow production pipeline, understanding how Spark breaks down your code is the key to performance tuning. Spark applications follow a strict hierarchy: Jobs > Stages > Tasks . Let’s break down exactly how this works. 1. High-Level Architecture Before we dive into the code, let’s look at the components that manage the execution: Driver: The brain. It converts your code into a Directed Acyclic Graph (DAG) and schedules tasks. DAG Scheduler: Splits the graph into Stages based on "shuffles." Task Scheduler: Sends the individual Tasks to the executors. Executors: The workers that actually run the tasks in parallel. 2. Real-World Code Walkthrough: The "Wide" Transformation Let’s analyze a common scenario: reading data, filtering, grouping, and saving. # 1. Read Data (Narrow) df = sp...
Read more

How Delta Lake Improves Query Performance with OPTIMIZE and File Compaction

By -
How Delta Lake Fixes Small File Problems Short answer: Too many small files can slow down queries and inflate metadata. Delta Lake’s OPTIMIZE command compacts small files into right-sized files, improving performance and reducing overhead. Why Small Files Hurt Performance When data is written in frequent small batches, it creates thousands of tiny files. This causes: I/O overhead: Queries must open and read many files, increasing latency and compute costs. Metadata bloat: Large transaction logs and planning overhead slow query planning. How Delta Lake Handles It Delta Lake provides the OPTIMIZE command to compact small files into fewer, larger files. This reduces overhead and speeds up queries. You can also use ZORDER BY to cluster data for faster lookups. -- Compact the entire table OPTIMIZE sales_delta; -- Compact a specific partition (e.g., date='2025-01-15') OPTIMIZE sales_delta WHERE date = '2025-01-15'; -- Optional: improve clustering for r...
Read more

Schema Enforcement and Schema Evolution in Delta Lake

By -
Listen and watch here Managing data consistency is one of the biggest challenges in big data systems. Delta Lake solves this problem with two powerful features: Schema Enforcement and Schema Evolution . Together, they ensure your data pipelines remain reliable while still allowing flexibility as business needs change. 🔍 What is Schema Enforcement? Schema Enforcement, also known as DataFrame write validation , ensures that the data being written to a Delta table matches the table’s schema. If the incoming data has mismatched columns or incompatible types, Delta Lake throws an error instead of silently corrupting the dataset. Example: Schema Enforcement -- Create a Delta table with specific schema CREATE TABLE people ( id INT, name STRING, age INT ) USING DELTA; -- Try inserting data with a wrong type INSERT INTO people VALUES (1, "Alice", "twenty-five"); Result: Delta Lake rejects this write because age expects an integer, not a string. This preven...
Read more