Understanding INSERT OVERWRITE and Time Travel in Delta Lake
I am a Tech Enthusiast having 13+ years of experience in ๐๐ as a ๐๐จ๐ง๐ฌ๐ฎ๐ฅ๐ญ๐๐ง๐ญ, ๐๐จ๐ซ๐ฉ๐จ๐ซ๐๐ญ๐ ๐๐ซ๐๐ข๐ง๐๐ซ, ๐๐๐ง๐ญ๐จ๐ซ, with 12+ years in training and mentoring in ๐๐จ๐๐ญ๐ฐ๐๐ซ๐ ๐๐ง๐ ๐ข๐ง๐๐๐ซ๐ข๐ง๐ , ๐๐๐ญ๐ ๐๐ง๐ ๐ข๐ง๐๐๐ซ๐ข๐ง๐ , ๐๐๐ฌ๐ญ ๐๐ฎ๐ญ๐จ๐ฆ๐๐ญ๐ข๐จ๐ง ๐๐ง๐ ๐๐๐ญ๐ ๐๐๐ข๐๐ง๐๐. I have ๐๐๐๐๐๐๐ ๐๐๐๐ ๐๐๐๐ 10,000+ ๐ฐ๐ป ๐ท๐๐๐๐๐๐๐๐๐๐๐๐ and ๐๐๐๐ ๐๐๐๐๐ ๐๐๐๐ ๐๐๐๐ 500+ ๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐ in the areas of ๐๐จ๐๐ญ๐ฐ๐๐ซ๐ ๐๐๐ฏ๐๐ฅ๐จ๐ฉ๐ฆ๐๐ง๐ญ, ๐๐๐ญ๐ ๐๐ง๐ ๐ข๐ง๐๐๐ซ๐ข๐ง๐ , ๐๐ฅ๐จ๐ฎ๐, ๐๐๐ญ๐ ๐๐ง๐๐ฅ๐ฒ๐ฌ๐ข๐ฌ, ๐๐๐ญ๐ ๐๐ข๐ฌ๐ฎ๐๐ฅ๐ข๐ณ๐๐ญ๐ข๐จ๐ง๐ฌ, ๐๐ซ๐ญ๐ข๐๐ข๐๐ข๐๐ฅ ๐๐ง๐ญ๐๐ฅ๐ฅ๐ข๐ ๐๐ง๐๐ ๐๐ง๐ ๐๐๐๐ก๐ข๐ง๐ ๐๐๐๐ซ๐ง๐ข๐ง๐ . I am interested in ๐ฐ๐ซ๐ข๐ญ๐ข๐ง๐ ๐๐ฅ๐จ๐ ๐ฌ, ๐ฌ๐ก๐๐ซ๐ข๐ง๐ ๐ญ๐๐๐ก๐ง๐ข๐๐๐ฅ ๐ค๐ง๐จ๐ฐ๐ฅ๐๐๐ ๐, ๐ฌ๐จ๐ฅ๐ฏ๐ข๐ง๐ ๐ญ๐๐๐ก๐ง๐ข๐๐๐ฅ ๐ข๐ฌ๐ฌ๐ฎ๐๐ฌ, ๐ซ๐๐๐๐ข๐ง๐ ๐๐ง๐ ๐ฅ๐๐๐ซ๐ง๐ข๐ง๐ new subjects.
INSERT OVERWRITE replaces the existing data in the table but preserves historical versions of the data.
Unlike CREATE OR REPLACE TABLE (CRAS), which modifies the schema, INSERT OVERWRITE generally only replaces the data.
Dataset Example
Let's assume we have two tables:
customers: Contains customer details.
sales: Stores sales transactions.
Step 1: Creating the Customers and Sales Tables
CREATE TABLE customers (
customer_id INT,
name STRING,
city STRING
) USING DELTA;
CREATE TABLE sales (
sales_id INT,
customer_id INT,
amount DECIMAL(10,2),
sale_date DATE
) USING DELTA;
Step 2: Inserting Initial Data
INSERT INTO customers VALUES (1, 'Alice', 'New York');
INSERT INTO customers VALUES (2, 'Bob', 'Los Angeles');
INSERT INTO customers VALUES (3, 'Charlie', 'Chicago');
INSERT INTO sales VALUES (101, 1, 200.50, '2024-01-10');
INSERT INTO sales VALUES (102, 2, 350.75, '2024-01-15');
INSERT INTO sales VALUES (103, 3, 500.00, '2024-01-20');
Step 3: Using INSERT OVERWRITE
INSERT OVERWRITE customer_sales
SELECT c.customer_id, c.name, s.sales_id, s.amount, s.sale_date
FROM customers c
INNER JOIN sales s ON s.customer_id = c.customer_id;
The first time this query runs, it creates the customer_sales table with the latest sales data.
The second time it runs, it overwrites the existing data while maintaining historical versions
Time Travel in Delta Lake
Since Delta Lake stores all historical changes, you can retrieve old versions of the table.
Step 4: Querying Previous Versions
To see all historical changes:
DESCRIBE HISTORY customer_sales;
To retrieve previous versions:
-- Fetch data from version 1 (initial data)
SELECT * FROM customer_sales VERSION AS OF 1;
-- Fetch data from version 2 (latest overwritten data)
SELECT * FROM customer_sales VERSION AS OF 2;
Key Differences: INSERT OVERWRITE vs. CREATE OR REPLACE TABLE



