Creating databases and tables in Hadoop - Performance & Efficiency

Time Complexity: Creating databases and tables

O(n)

Understanding Time Complexity

When we create databases and tables in Hadoop, we want to know how long it takes as we add more commands or data.

We ask: How does the time to create these structures grow when we create more of them?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

CREATE DATABASE IF NOT EXISTS sales_db;
USE sales_db;
CREATE TABLE IF NOT EXISTS transactions (
  id INT,
  amount FLOAT,
  date STRING
) STORED AS PARQUET;

CREATE TABLE IF NOT EXISTS customers (
  customer_id INT,
  name STRING
) STORED AS ORC;

This code creates one database and two tables inside it, defining their structure and storage format.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Executing each CREATE statement one by one.
• How many times: Once per database or table creation command.

How Execution Grows With Input

Each new database or table requires a separate command to run.

Input Size (n)	Approx. Operations
10	10 commands executed
100	100 commands executed
1000	1000 commands executed

Pattern observation: The time grows directly with the number of create commands.

Final Time Complexity

Time Complexity: O(n)

This means the time to create databases and tables grows in a straight line as you add more create commands.

Common Mistake

[X] Wrong: "Creating multiple tables happens all at once, so time stays the same no matter how many tables."

[OK] Correct: Each create command runs separately, so more tables mean more commands and more time.

Interview Connect

Understanding how time grows with commands helps you explain system behavior clearly and shows you think about efficiency in real projects.

Self-Check

"What if we batch multiple table creations into a single script? How would the time complexity change?"