Skip to main content

Composer - GCP




the DAG files are stored within a "dags" folder, which resides inside of a Cloud Storage bucket, that is created when a Cloud Composer environment is created.




inside the DAG file there will be the default py file for orchestration.

you can create the number of DAG files and upload into this folder to create the workflow

if you click on the files, it will lead to airflow monitoring under graph you can see DAG and operator (task) , and under code ,you can see the code for orchestration 



if the DAG is yellow in color that means it's not working properly then we have to debug if its in green color its works properly .


from airflow import DAG
from airflow.operators.bash import BashOperator
from datetime import datetime, timedelta

default_args = {
    'owner': 'your_name',
    'start_date': datetime(2023, 10, 26),
    'retries': 1,
    'retry_delay': timedelta(minutes=5),
    'dagrun_timeout': timedelta(hours=2),
}

with DAG(
    dag_id='my_data_pipeline',  # DAG Name
    schedule_interval='@daily',  # Schedule interval
    default_args=default_args,
    catchup=False, The catchup parameter determines whether Airflow should "catch up" on past scheduled runs that were missed.
) as dag:
    task1 = BashOperator(
        task_id='extract_data',  # Task ID
        bash_command='echo "Extracting data..."',
    )

    task2 = BashOperator(
        task_id='transform_data',  # Task ID
        bash_command='echo "Transforming data..."',
    )

    task1 >> task2  # Define task dependencies, >> operator defines the order in which tasks should be executed

Key Points:

  • DAG parameters control the overall behavior of the workflow.
  • Operator parameters define the individual steps within the workflow.
  • task_id values must be unique within a DAG.
  • The dag_id must be unique across all dags inside of the airflow environment.
  • The schedule_interval is what tells airflow when to run the dag.
  • The dagrun_timeout is a safety net.

I hope this helps clarify these important Airflow concepts.

Comments

Popular posts from this blog

Entity Relationship (ER) Diagram Model with DBMS Example

Reference :   Entity Relationship (ER) Diagram Model with DBMS Example What is ER Diagram? ER Diagram  stands for Entity Relationship Diagram, also known as ERD is a diagram that displays the relationship of entity sets stored in a database. In other words, ER diagrams help to explain the logical structure of databases. ER diagrams are created based on three basic concepts: entities, attributes and relationships. ER Diagrams contain different symbols that use rectangles to represent entities, ovals to define attributes and diamond shapes to represent relationships. At first look, an ER diagram looks very similar to the flowchart. However, ER Diagram includes many specialized symbols, and its meanings make this model unique. The purpose of ER Diagram is to represent the entity framework infrastructure. Entity Relationship Diagram Example Table of Content: What is ER Diagram? What is ER Model? History of ER models Why use ER Diagrams? Facts about ER Diagram Model ER Diagram...

SQL Joins and advanced joins and Subqueries

  Refernce :  Expert Guide to Advanced SQL Joins: What You Need to Know It's helpful to visualize how these different SQL joins work. Here's a breakdown in a table-like format, along with explanations: SQL Join Types Overview Join Type Description Key Characteristics Use Cases INNER JOIN Returns rows where there is a match in both tables. - Shows only matching records. - Excludes unmatched rows from both tables. - Retrieving related data that exists in both tables. - Finding records with corresponding entries in another table. LEFT OUTER JOIN (LEFT JOIN) Returns all rows from the left table, and the matched rows from the right table. - Includes all records from the left table. - Fills in NULL values for columns from the right table where there's no match. - Retrieving all records from one table and their related data from another, even if some records don't have matches. - Finding records in one table that don't have corresponding entries in another. RIGHT OUTER JO...

GIT BASH

  Bash Shell: Git Bash uses the Bash (Bourne Again SHell) command-line interpreter. This means you can use many of the same commands you'd find in a Linux or macOS terminal. Git Integration: Git Bash is tightly integrated with Git, making it easy to execute Git commands Essential Commands: Navigation: pwd : Prints the current working directory. ls : Lists files and directories in the current directory. cd <directory> : Changes the current directory. cd .. : Moves to the parent directory. File Management: mkdir <directory> : Creates a new directory. touch <file> : Creates a new file. rm <file> : Removes a file. rmdir <directory> : Removes an empty directory. Git Commands: git init : Initializes a new Git repository. git clone <repository URL> : Clones an existing Git repository. git status : Displays the status of your working directory. git add <file> : Adds a file to the staging area. git commit -m "commit message" : Commits chan...