Data pipeline patterns in GCP - Commands & Configuration

Introduction

Data pipelines move and transform data from one place to another automatically. They help organize data flow so you can analyze or use it easily without manual work.

When you want to collect data from multiple sources like databases and files into one place.

When you need to clean or change data format before using it in reports or apps.

When you want to move data regularly, like every hour or day, without doing it by hand.

When you want to combine data from different systems to get a full picture.

When you want to automate data tasks so your team can focus on analysis, not moving data.

Config File - dataflow_pipeline.py

dataflow_pipeline.py

import apache_beam as beam
from apache_beam.options.pipeline_options import PipelineOptions

class FormatData(beam.DoFn):
    def process(self, element):
        # Example: convert all text to lowercase
        yield element.lower()

pipeline_options = PipelineOptions(
    project='example-project',
    region='us-central1',
    runner='DataflowRunner',
    temp_location='gs://example-bucket/temp',
    staging_location='gs://example-bucket/staging'
)

with beam.Pipeline(options=pipeline_options) as p:
    (p
     | 'ReadFromText' >> beam.io.ReadFromText('gs://example-bucket/input/data.txt')
     | 'FormatData' >> beam.ParDo(FormatData())
     | 'WriteToText' >> beam.io.WriteToText('gs://example-bucket/output/formatted_data')
    )

This Python file defines a simple data pipeline using Apache Beam on Google Cloud Dataflow.

FormatData class changes data to lowercase as an example transformation.

pipeline_options sets project info, region, and storage locations needed to run the pipeline on Dataflow.

The pipeline reads text data from a Cloud Storage bucket, processes it, and writes the output back to another bucket.

Commands

This command runs the data pipeline script. It starts the pipeline on Google Cloud Dataflow, which reads, processes, and writes data automatically.

Terminal

python3 dataflow_pipeline.py

Expected Output

INFO:apache_beam.runners.dataflow.dataflow_runner:Job 2024-0000000000000000 starting on project example-project

INFO:apache_beam.runners.dataflow.dataflow_runner:Job 2024-0000000000000000 is in state JOB_STATE_RUNNING

INFO:apache_beam.runners.dataflow.dataflow_runner:Job 2024-0000000000000000 finished successfully

This command lists the files in the output Cloud Storage bucket to verify the pipeline wrote the processed data.

Terminal

gsutil ls gs://example-bucket/output/

Expected Output

gs://example-bucket/output/formatted_data-00000-of-00001

This command shows the content of the output file to check the data was transformed as expected.

Terminal

gsutil cat gs://example-bucket/output/formatted_data-00000-of-00001

Expected Output

example line one

another example line

more data here

Key Concept

If you remember nothing else from this pattern, remember: data pipelines automate moving and changing data so you don’t have to do it manually.

Common Mistakes

Not setting the correct project or bucket names in the pipeline options

The pipeline will fail to start or cannot read/write data if these values are wrong.

Always double-check your Google Cloud project ID and Cloud Storage bucket names before running the pipeline.

Running the pipeline without having the input data file in the specified bucket

The pipeline will error because it cannot find the data to process.

Upload your input data file to the Cloud Storage bucket path before running the pipeline.

Not waiting for the pipeline job to finish before checking output files

Output files may not exist yet or be incomplete if the job is still running.

Check the job status and wait until it finishes successfully before verifying output.

Summary

Write a pipeline script that reads, processes, and writes data using Apache Beam on Google Cloud Dataflow.

Run the pipeline script to start the automated data processing job in the cloud.

Verify the output files in Cloud Storage to confirm the pipeline worked as expected.

Practice

1. Which Google Cloud service is best suited for real-time messaging in a data pipeline?

easy

A. Cloud Storage

B. BigQuery

C. Pub/Sub

D. Cloud Functions

Solution

1. Step 1: Understand real-time messaging needs

   Real-time messaging requires a service that can quickly send and receive messages between components.

2. Step 2: Identify Google Cloud services for messaging

   Pub/Sub is designed for real-time messaging, while BigQuery is for analytics, Cloud Storage for file storage, and Cloud Functions for event-driven compute.

3. Final Answer:

   Pub/Sub -> Option C

4. Quick Check:

   Real-time messaging = Pub/Sub [OK]

Hint: Real-time messaging in GCP? Think Pub/Sub first [OK]

Common Mistakes:

• Confusing BigQuery as a messaging service
• Choosing Cloud Storage for streaming data
• Selecting Cloud Functions instead of messaging service

2. Which of the following is the correct syntax to create a Dataflow pipeline in Python using Apache Beam?

easy

A. pipeline = beam.Pipeline(options=options)

B. pipeline = Dataflow(options)

C. pipeline = beam.Create(options)

D. pipeline = DataflowPipeline(options=options)

Solution

1. Step 1: Recall Apache Beam pipeline creation syntax

   Apache Beam pipelines are created using beam.Pipeline with options passed as a parameter.

2. Step 2: Compare options

   pipeline = beam.Pipeline(options=options) matches the correct syntax. Other options use incorrect class names or methods.

3. Final Answer:

   pipeline = beam.Pipeline(options=options) -> Option A

4. Quick Check:

   Apache Beam pipeline creation = beam.Pipeline [OK]

Hint: Beam pipelines start with beam.Pipeline(options=...) [OK]

Common Mistakes:

• Using Dataflow instead of beam.Pipeline
• Confusing Create with pipeline creation
• Incorrect class names like DataflowPipeline

3. Given this simplified Dataflow pipeline code snippet, what will be the output in BigQuery?

p = beam.Pipeline(options=options)
(p
 | 'Read' >> beam.io.ReadFromPubSub(subscription='sub')
 | 'Parse' >> beam.Map(lambda x: x.decode('utf-8'))
 | 'Write' >> beam.io.WriteToBigQuery('project:dataset.table'))
p.run()

medium

A. Data will be stored in Cloud Storage instead of BigQuery

B. Data from Pub/Sub messages decoded and stored in BigQuery table

C. Pipeline will fail due to missing schema in WriteToBigQuery

D. Raw Pub/Sub messages stored as bytes in BigQuery

Solution

1. Step 1: Analyze pipeline steps

   The pipeline reads messages from Pub/Sub, decodes bytes to strings, then writes to BigQuery.

2. Step 2: Understand output behavior

   Since messages are decoded before writing, the data stored in BigQuery will be the decoded string form.

3. Final Answer:

   Data from Pub/Sub messages decoded and stored in BigQuery table -> Option B

4. Quick Check:

   Decoded Pub/Sub data written to BigQuery = Data from Pub/Sub messages decoded and stored in BigQuery table [OK]

Hint: Decoded Pub/Sub data goes to BigQuery if WriteToBigQuery used [OK]

Common Mistakes:

• Assuming raw bytes are stored without decoding
• Thinking pipeline fails without explicit schema (default schema can be inferred)
• Confusing output destination as Cloud Storage

4. You have a Dataflow pipeline that reads from Pub/Sub but fails with a permission error. What is the most likely cause?

medium

A. The Pub/Sub topic does not exist

B. BigQuery dataset is not created

C. The Dataflow pipeline code has syntax errors

D. The service account running Dataflow lacks Pub/Sub Subscriber role

Solution

1. Step 1: Identify permission error context

   Permission errors usually mean the service account lacks rights to access a resource.

2. Step 2: Match error to resource

   Since the pipeline reads from Pub/Sub, the service account needs the Subscriber role on the Pub/Sub topic.

3. Final Answer:

   The service account running Dataflow lacks Pub/Sub Subscriber role -> Option D

4. Quick Check:

   Permission error reading Pub/Sub = missing Subscriber role [OK]

Hint: Permission errors often mean missing roles on resources [OK]

Common Mistakes:

• Assuming syntax errors cause permission errors
• Thinking topic absence causes permission errors
• Confusing BigQuery dataset issues with Pub/Sub permissions

5. You want to build a data pipeline that ingests streaming IoT sensor data, processes it in real-time, and stores aggregated results hourly in BigQuery. Which pattern best fits this use case?

hard

A. Use Pub/Sub for ingestion, Dataflow streaming for processing with windowing, then write to BigQuery

B. Use Cloud Storage for ingestion, batch Dataflow jobs for processing, then write to BigQuery

C. Use BigQuery streaming inserts directly from IoT devices

D. Use Cloud Functions triggered by Cloud Storage uploads to process data

Solution

1. Step 1: Identify streaming ingestion and processing needs

   IoT sensor data is streaming and requires real-time processing with time-based aggregation.

2. Step 2: Match GCP services to requirements

   Pub/Sub handles streaming ingestion, Dataflow streaming supports windowed aggregation, and BigQuery stores results efficiently.

3. Final Answer:

   Use Pub/Sub for ingestion, Dataflow streaming for processing with windowing, then write to BigQuery -> Option A

4. Quick Check:

   Streaming ingestion + windowed processing + BigQuery = Use Pub/Sub for ingestion, Dataflow streaming for processing with windowing, then write to BigQuery [OK]

Hint: Streaming + windowed aggregation = Pub/Sub + Dataflow + BigQuery [OK]

Common Mistakes:

• Using batch processing for streaming data
• Trying to write streaming data directly to BigQuery without processing
• Using Cloud Storage which is for batch files, not streaming