Why ingestion pipelines feed the data lake in Hadoop - Performance Analysis

Time Complexity: Why ingestion pipelines feed the data lake

O(n)

Understanding Time Complexity

We want to understand how the time to move data into a data lake grows as the data size increases.

How does the ingestion pipeline handle larger amounts of data efficiently?

Scenario Under Consideration

Analyze the time complexity of this Hadoop ingestion pipeline snippet.

// Hadoop MapReduce job to ingest data into data lake
public class DataIngestionMapper extends Mapper {
  public void map(LongWritable key, Text value, Context context) throws IOException, InterruptedException {
    // Process each line of input data
    context.write(value, NullWritable.get());
  }
}

// No reducer needed, data is directly stored in data lake

This code reads input data line by line and writes it directly to the data lake storage.

Identify Repeating Operations

Look at what repeats as data size grows.

• Primary operation: Processing each line of input data once in the mapper.
• How many times: Once per input line, so as many times as there are lines.

How Execution Grows With Input

As the number of input lines grows, the total work grows in the same way.

Input Size (n)	Approx. Operations
10	10 processing steps
100	100 processing steps
1000	1000 processing steps

Pattern observation: The work grows directly with the number of input lines.

Final Time Complexity

Time Complexity: O(n)

This means the time to ingest data grows linearly with the amount of data.

Common Mistake

[X] Wrong: "The ingestion time stays the same no matter how much data we have."

[OK] Correct: Each line must be processed, so more data means more work and more time.

Interview Connect

Understanding how data ingestion scales helps you explain real-world data pipeline performance clearly and confidently.

Self-Check

"What if the ingestion pipeline added a reducer step that aggregates data? How would the time complexity change?"

Practice

1. Why do ingestion pipelines feed data into a data lake?

easy

A. To collect raw data from multiple sources in one place

B. To delete old data automatically

C. To convert all data into a single format immediately

D. To prevent data from being accessed by users

Solution

1. Step 1: Understand the role of ingestion pipelines

   Ingestion pipelines gather data from many different sources.

2. Step 2: Understand the purpose of a data lake

   A data lake stores raw data centrally for easy access and analysis later.

3. Final Answer:

   To collect raw data from multiple sources in one place -> Option A

4. Quick Check:

   Ingestion pipelines feed raw data to data lakes = A [OK]

Hint: Remember: pipelines bring raw data together [OK]

Common Mistakes:

• Thinking pipelines delete data
• Assuming data is converted immediately
• Believing data lakes block user access

2. Which of the following is a correct tool used in ingestion pipelines for feeding data lakes?

easy

A. WordPress

B. Photoshop

C. Excel

D. Hadoop

Solution

1. Step 1: Identify tools related to data ingestion

   Hadoop is a big data tool used for storing and processing large datasets.

2. Step 2: Check other options

   Photoshop, Excel, and WordPress are not designed for data ingestion pipelines.

3. Final Answer:

   Hadoop -> Option D

4. Quick Check:

   Hadoop is a data ingestion tool = A [OK]

Hint: Pick big data tools, not office or design apps [OK]

Common Mistakes:

• Confusing data tools with office software
• Choosing popular but unrelated software
• Ignoring Hadoop's role in data pipelines

3. Consider this code snippet using Apache NiFi to ingest data:

flowFile = session.get()
if flowFile is None:
    session.commit()
    exit()
flowFile = session.putAttribute(flowFile, "source", "sensor1")
session.transfer(flowFile, REL_SUCCESS)

What does this pipeline step do?

medium

A. It deletes the data from the pipeline

B. It adds a source attribute and sends data forward

C. It converts data to CSV format

D. It stops the pipeline permanently

Solution

1. Step 1: Analyze the code actions

   The code gets a data flow file, adds an attribute named 'source' with value 'sensor1'.

2. Step 2: Understand the transfer step

   It then transfers the flow file to the success relationship, moving data forward.

3. Final Answer:

   It adds a source attribute and sends data forward -> Option B

4. Quick Check:

   Attribute added + transfer = C [OK]

Hint: Look for attribute changes and transfer commands [OK]

Common Mistakes:

• Thinking data is deleted
• Assuming format conversion happens here
• Believing pipeline stops permanently

4. This ingestion pipeline code snippet has an error:

data = kafka_consumer.poll()
if data:
print('Data received:', data)
process(data)

What is the error and how to fix it?

medium

A. Indentation error; indent the print and process lines

B. Syntax error; replace poll() with consume()

C. Runtime error; data variable is undefined

D. Logical error; should check data length instead of truthiness

Solution

1. Step 1: Identify the error in code structure

   The print and process lines are not indented under the if statement, causing an indentation error.

2. Step 2: Fix the indentation

   Indent these lines to be inside the if block to run only when data exists.

3. Final Answer:

   Indentation error; indent the print and process lines -> Option A

4. Quick Check:

   Indentation fixes code error = B [OK]

Hint: Check indentation after if statements [OK]

Common Mistakes:

• Confusing method names
• Assuming variable is undefined
• Overthinking data checks

5. You want to build an ingestion pipeline that feeds a data lake with streaming data from multiple sensors. Which approach best ensures data is stored raw and ready for future analysis?

hard

A. Use batch uploads once a day to reduce pipeline complexity

B. Transform data into summaries before storing to reduce storage needs

C. Use Kafka to collect streams, then store raw data in Hadoop HDFS without transformation

D. Store data only after converting to JSON format and filtering out duplicates

Solution

1. Step 1: Understand raw data storage needs

   Storing raw data means saving original data without changes for flexible analysis later.

2. Step 2: Evaluate options for streaming ingestion

   Kafka is designed for streaming data collection; Hadoop HDFS stores large raw datasets efficiently.

3. Step 3: Compare other options

   Transforming or filtering data early loses raw details; batch uploads delay data availability.

4. Final Answer:

   Use Kafka to collect streams, then store raw data in Hadoop HDFS without transformation -> Option C

5. Quick Check:

   Raw streaming data + Hadoop storage = D [OK]

Hint: Keep data raw and streaming for best analysis [OK]

Common Mistakes:

• Filtering data too early
• Using batch instead of streaming
• Converting formats before storage