Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Tutorials
    • All tutorials
    • Unassisted deployment of the Apache Kafka® web interface
    • Upgrading a Managed Service for Apache Kafka® cluster to migrate from ZooKeeper to KRaft
    • Migrating a database from a third-party Apache Kafka® cluster to Managed Service for Apache Kafka®
    • Moving data between Managed Service for Apache Kafka® clusters using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for YDB to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for ClickHouse® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Yandex MPP Analytics for PostgreSQL using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Yandex StoreDoc using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for MySQL® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for OpenSearch using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for PostgreSQL using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for YDB using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Data Streams using Data Transfer
    • Delivering data from Data Streams to Managed Service for YDB using Data Transfer
    • Delivering data from Data Streams to Managed Service for Apache Kafka® using Data Transfer
    • YDB change data capture and delivery to YDS
    • Configuring Kafka Connect to work with a Managed Service for Apache Kafka® cluster
    • Synchronizing Apache Kafka® topics in Object Storage with no web access
    • Monitoring message loss in an Apache Kafka® topic
    • Automating Query tasks with Managed Service for Apache Airflow™
    • Sending requests to the Yandex Cloud API via the Yandex Cloud Python SDK
    • Configuring an SMTP server to send e-mail notifications
    • Adding data to a ClickHouse® DB
    • Migrating data to Managed Service for ClickHouse® using ClickHouse® tools
    • Migrating data to Managed Service for ClickHouse® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for ClickHouse® using Data Transfer
    • Asynchronously replicating data from PostgreSQL to ClickHouse®
    • Exchanging data between Managed Service for ClickHouse® and Yandex Data Processing
    • Configuring Managed Service for ClickHouse® for Graphite
    • Fetching data from Managed Service for Apache Kafka® to Managed Service for ClickHouse®
    • Fetching data from Managed Service for Apache Kafka® to ksqlDB
    • Fetching data from RabbitMQ to Managed Service for ClickHouse®
    • Saving a data stream from Data Streams to Managed Service for ClickHouse®
    • Asynchronous replication of data from Yandex Metrica to ClickHouse® using Data Transfer
    • Using hybrid storage in Managed Service for ClickHouse®
    • Sharding Managed Service for ClickHouse® tables
    • Loading data from Yandex Direct to a Managed Service for ClickHouse® data mart using Cloud Functions, Object Storage, and Data Transfer
    • Loading data from Object Storage to Managed Service for ClickHouse® using Data Transfer
    • Migrating data with change of storage from Managed Service for OpenSearch to Managed Service for ClickHouse® using Data Transfer
    • Loading data from Managed Service for YDB to Managed Service for ClickHouse® using Data Transfer
    • Yandex Managed Service for ClickHouse® integration with Microsoft SQL Server via ClickHouse® JDBC Bridge
    • Migrating databases from Google BigQuery to Managed Service for ClickHouse®
    • Yandex Managed Service for ClickHouse® integration with Oracle via ClickHouse® JDBC Bridge
    • Configuring Cloud DNS to access a Managed Service for ClickHouse® cluster from other cloud networks
    • Migrating a Yandex Data Processing HDFS cluster to a different availability zone
    • Importing data from Managed Service for MySQL® to Yandex Data Processing using Sqoop
    • Importing data from Managed Service for PostgreSQL to Yandex Data Processing using Sqoop
    • Mounting Object Storage buckets to the file system of Yandex Data Processing hosts
    • Working with Apache Kafka® topics using Yandex Data Processing
    • Automating operations with Yandex Data Processing using Managed Service for Apache Airflow™
    • Shared use of Yandex Data Processing tables through Apache Hive™ Metastore
    • Transferring metadata across Yandex Data Processing clusters using Apache Hive™ Metastore
    • Importing data from Object Storage, processing it, and exporting it to Managed Service for ClickHouse®
    • Migrating collections from a third-party MongoDB cluster to Yandex StoreDoc
    • Migrating data to Yandex StoreDoc
    • Migrating Yandex StoreDoc cluster from 4.4 to 6.0
    • Sharding Yandex StoreDoc collections
    • Yandex StoreDoc performance analysis and tuning
    • Managed Service for MySQL® performance analysis and tuning
    • Syncing data from a third-party MySQL® cluster to Managed Service for MySQL® using Data Transfer
    • Migrating a database from Managed Service for MySQL® to a third-party MySQL® cluster
    • Migrating a database from Managed Service for MySQL® to Object Storage using Data Transfer
    • Migrating data from Object Storage to Managed Service for MySQL® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Debezium
    • Migrating a database from Managed Service for MySQL® to Managed Service for YDB using Data Transfer
    • MySQL® change data capture and delivery to YDS
    • Migrating data from Managed Service for MySQL® to Managed Service for PostgreSQL using Data Transfer
    • Migrating data from AWS RDS for PostgreSQL to Managed Service for PostgreSQL using Data Transfer
    • Migrating data from Managed Service for MySQL® to Yandex MPP Analytics for PostgreSQL using Data Transfer
    • Configuring an index policy in Managed Service for OpenSearch
    • Migrating data from a third-party OpenSearch cluster to Managed Service for OpenSearch using Data Transfer
    • Loading data from Managed Service for OpenSearch to Object Storage using Data Transfer
    • Migrating data from Managed Service for OpenSearch to Managed Service for YDB using Data Transfer
    • Copying data from Managed Service for OpenSearch to Yandex MPP Analytics for PostgreSQL using Yandex Data Transfer
    • Migrating data from Managed Service for PostgreSQL to Managed Service for OpenSearch using Data Transfer
    • Authenticating a Managed Service for OpenSearch cluster in OpenSearch Dashboards using Keycloak
    • Using the yandex-lemmer plugin in Managed Service for OpenSearch
    • Creating a PostgreSQL cluster for 1C:Enterprise
    • Searching for the Managed Service for PostgreSQL cluster performance issues
    • Managed Service for PostgreSQL performance analysis and tuning
    • Logical replication in PostgreSQL
    • Migrating a database from a third-party PostgreSQL cluster to Managed Service for PostgreSQL
    • Migrating a database from Managed Service for PostgreSQL
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for PostgreSQL to Managed Service for YDB using Data Transfer
    • Migrating a database from Managed Service for PostgreSQL to Object Storage
    • Migrating data from Object Storage to Managed Service for PostgreSQL using Data Transfer
    • PostgreSQL change data capture and delivery to YDS
    • Migrating data from Managed Service for PostgreSQL to Managed Service for MySQL® using Data Transfer
    • Migrating data from Managed Service for PostgreSQL to Managed Service for OpenSearch using Data Transfer
    • Fixing string sorting issues in PostgreSQL after upgrading glibc
    • Migrating a database from Greenplum® to ClickHouse®
    • Migrating a database from Greenplum® to PostgreSQL
    • Exporting Greenplum® data to a cold storage in Object Storage
    • Loading data from Object Storage to Yandex MPP Analytics for PostgreSQL using Data Transfer
    • Copying data from Managed Service for OpenSearch to Yandex MPP Analytics for PostgreSQL using Yandex Data Transfer
    • Creating an external table from an Object Storage bucket table using a configuration file
    • Getting data from external sources using named queries in Greenplum®
    • Migrating a database from a third-party Valkey™ cluster to Yandex Managed Service for Valkey™
    • Using a Yandex Managed Service for Valkey™ cluster as a PHP session storage
    • Loading data from Object Storage to Managed Service for YDB using Data Transfer
    • Loading data from Managed Service for YDB to Object Storage using Data Transfer
    • Processing Audit Trails events
    • Processing Cloud Logging logs
    • Processing Debezium CDC streams
    • Analyzing data with Jupyter
    • Processing files with usage details in Yandex Cloud Billing
    • Ingesting data into storage systems
    • Smart log processing
    • Data transfer in microservice architectures
    • Migrating data to Object Storage using Data Transfer
    • Migrating data from a third-party Greenplum® or PostgreSQL cluster to Yandex MPP Analytics for PostgreSQL using Data Transfer
    • Migrating Yandex StoreDoc clusters
    • Migrating MySQL® clusters
    • Migrating to a third-party MySQL® cluster
    • Migrating PostgreSQL clusters
    • Creating a schema registry to deliver data in Debezium CDC format from Apache Kafka®
    • Automating operations using Yandex Managed Service for Apache Airflow™
    • Working with an Object Storage table from a PySpark job
    • Integrating Yandex Managed Service for Apache Spark™ with Apache Hive™ Metastore
    • Running a PySpark job using Yandex Managed Service for Apache Airflow™
    • Using Yandex Object Storage in Yandex Managed Service for Apache Spark™

In this article:

  • Required paid resources
  • Set up your infrastructure
  • Prepare a PySpark job
  • Prepare and run a DAG file
  • Check the result
  • Delete the resources you created
  1. Building a data platform
  2. Automating operations using Yandex Managed Service for Apache Airflow™

Automating operations using Yandex Managed Service for Apache Airflow™

Written by
Yandex Cloud
Updated at December 3, 2025
  • Required paid resources
  • Set up your infrastructure
  • Prepare a PySpark job
  • Prepare and run a DAG file
  • Check the result
  • Delete the resources you created

Warning

This tutorial was tested on clusters with the Apache Airflow™ version below 3.0.

In Yandex Managed Service for Apache Airflow™, you can create a directed acyclic graph (DAG) to automate your operations in Yandex Managed Service for Apache Spark™. Below is an example of a DAG that includes a number of tasks:

  1. Create an Apache Spark™ cluster.
  2. Run a PySpark job.
  3. Delete the Apache Spark™ cluster.

With a DAG like this, a cluster is short-lived. In a cluster, you can engage higher capacity resources and process more data quickly.

In this DAG, an Apache Spark™ cluster is created. We use a Apache Hive™ Metastore cluster to store tabular metadata in the example below. The saved metadata can then be used by another Apache Spark™ cluster.

To use Yandex Managed Service for Apache Spark™ in Yandex Managed Service for Apache Airflow™:

  1. Set up your infrastructure.
  2. Prepare a PySpark job.
  3. Prepare and run a DAG file.
  4. Check the result.

If you no longer need the resources you created, delete them.

Required paid resourcesRequired paid resources

The support cost includes:

  • Apache Airflow™ cluster fee: computing resources of the cluster components (see Yandex Managed Service for Apache Airflow™ pricing).
  • Fee for computing resources in a Apache Hive™ Metastore cluster (see Yandex MetaData Hub pricing).
  • Object Storage bucket fee: Covers data storage and bucket operations (see Object Storage pricing).
  • Fee for collecting and storing logs (see Cloud Logging pricing).

Set up your infrastructureSet up your infrastructure

The example below illustrates two scenarios. Select the one you find most relevant:

  • High security level. This is a recommended scenario, as it respects the principle of least privilege. This scenario entails the following:

    • Splitting access permissions across different service accounts. You have to create a separate service account for each cluster and assign to it only the roles required for this account's cluster to operate.
    • Using multiple buckets for different tasks and storing different data in separate buckets. For example, a DAG is loaded to one bucket, while the results of running a PySpark job are written to another bucket.
    • Setting up security groups. This way, you can restrict traffic and grant access only to authorized resources.
  • Simplified setup. This scenario implies a lower security level:

    • Using a single service account with more privileges than required.
    • Storing all data in a single bucket but in different folders.
    • No security groups are set up.
High security level
Simplified setup

Set up the infrastructure:

  1. Create service accounts with the following roles:

    Service account

    Roles

    airflow-agent for an Apache Airflow™ cluster

    • managed-airflow.integrationProvider: To enable the Apache Airflow™ cluster to interact with other resources.
    • managed-spark.editor: To manage an Apache Spark™ cluster from a DAG.
    • iam.serviceAccounts.user: To specify the spark-agent service account when creating an Apache Spark™ cluster.
    • vpc.user: To use the Yandex Virtual Private Cloud subnet in the Apache Airflow™ cluster.
    • logging.editor: To work with log groups.
    • logging.reader: To read logs.
    • mdb.viewer: To get operation statuses.
    • managed-metastore.viewer: To view information about Apache Hive™ Metastore clusters.

    metastore-agent for an Apache Hive™ Metastore cluster

    • managed-metastore.integrationProvider: To enable the Apache Hive™ Metastore cluster to interact with other resources.

    spark-agent for an Apache Spark™ cluster

    • managed-spark.integrationProvider: To enable the Apache Spark™ cluster to interact with other resources.
  2. Create buckets:

    • <bucket_for_Airflow_DAG_source_code>.
    • <bucket_for_PySpark_job_source_code>.
    • <bucket_for_PySpark_job_output_data>.

    You need multiple buckets with different access permissions.

  3. Grant permissions for the buckets as follows:

    • <bucket_for_Airflow_DAG_source_code>: READ permission to the airflow-agent service account.
    • <bucket_for_PySpark_job_source_code>: READ permission to the spark-agent service account.
    • <bucket_for_PySpark_job_output_data>: READ and WRITE permissions to the spark-agent and metastore-agent service accounts.
  4. Create a cloud network named datalake-network.

    This will automatically create three subnets in different availability zones.

  5. For the Apache Hive™ Metastore cluster, create a security group named metastore-sg in datalake-network. Add the following rules to it:

    • For incoming client traffic:

      • Port range: 30000-32767
      • Protocol: Any
      • Source: CIDR
      • CIDR blocks: 0.0.0.0/0
    • For incoming load balancer traffic:

      • Port range: 10256
      • Protocol: Any
      • Source: Load balancer health checks
  6. For the Apache Airflow™ cluster, create a security group named airflow-sg in datalake-network. Add the following rule to it:

    • For outgoing HTTPS traffic:

      • Port range: 443
      • Protocol: TCP
      • Destination: CIDR
      • CIDR blocks: 0.0.0.0/0
  7. For the Apache Spark™ cluster, create a security group named spark-sg in datalake-network. Add the following rule to it:

    • For outgoing traffic, to allow Apache Spark™ cluster connections to Apache Hive™ Metastore:

      • Port range: 9083
      • Protocol: Any
      • Destination: CIDR
      • CIDR blocks: 0.0.0.0/0
  8. Create a Apache Hive™ Metastore cluster with the following parameters:

    • Service account: metastore-agent
    • Version: 3.1
    • Network: datalake-network
    • Subnet: datalake-network-ru-central1-a
    • Security group: metastore-sg

    Note

    Wait for the operation to complete.

  9. Create a Managed Service for Apache Airflow™ cluster with the following parameters:

    • Service account: airflow-agent
    • Availability zone: ru-central1-a
    • Network: datalake-network
    • Subnet: datalake-network-ru-central1-a
    • Security group: airflow-sg
    • Bucket name: <bucket_for_Airflow_DAG_source_code>

Set up the infrastructure:

  1. Create a service account named integration-agent with the following roles:

    • managed-airflow.integrationProvider: To enable the Apache Airflow™ cluster to interact with other resources.
    • managed-spark.editor: To manage an Apache Spark™ cluster from a DAG.
    • iam.serviceAccounts.user: To specify the spark-agent service account when creating an Apache Spark™ cluster.
    • vpc.user: To use the Yandex Virtual Private Cloud subnet in the Apache Airflow™ cluster.
    • logging.editor: To work with log groups.
    • logging.reader: To read logs.
    • mdb.viewer: To get operation statuses.
    • managed-metastore.viewer: To view information about Apache Hive™ Metastore clusters.
    • managed-metastore.integrationProvider: To enable the Apache Hive™ Metastore cluster to interact with other resources.
    • managed-spark.integrationProvider: To enable the Apache Spark™ cluster to interact with other resources.
  2. Create a bucket named <bucket_for_jobs_and_data> and grant READ and WRITE permissions to the integration-agent service account.

  3. Create a cloud network named datalake-network.

    This will automatically create three subnets in different availability zones and a security group.

  4. Create a Apache Hive™ Metastore cluster with the following parameters:

    • Service account: integration-agent
    • Network: datalake-network
    • Subnet: datalake-network-ru-central1-a
    • Security group: Default group in datalake-network

    Note

    Wait for the operation to complete.

  5. Create a Managed Service for Apache Airflow™ cluster with the following parameters:

    • Service account: integration-agent
    • Availability zone: ru-central1-a
    • Network: datalake-network
    • Subnet: datalake-network-ru-central1-a
    • Security group: Default group in datalake-network
    • Bucket name: <bucket_for_jobs_and_data>

Prepare a PySpark jobPrepare a PySpark job

For a PySpark job, we will use a Python script that creates a table and is stored in the Object Storage bucket. Prepare a script file:

High security level
Simplified setup
  1. Create a local file named job_with_table.py and paste the following script to it:

    import random
    from pyspark.sql import SparkSession
    
    
    def prepare_table(spark, database, table):
        create_database_sql = "create database if not exists {database}"
        create_table_sql = """
        create table if not exists {database}.{table} (
            id int,
            value double
        )
        using iceberg
        """
        truncate_table_sql = "truncate table {database}.{table}"
    
        spark.sql(create_database_sql.format(database=database))
        spark.sql(create_table_sql.format(database=database, table=table))
        spark.sql(truncate_table_sql.format(database=database, table=table))
    
    
    def write_data(spark, database, table):
        data = [(i, random.random()) for i in range(100_000)]
        # Creating a dataframe
        df = spark.createDataFrame(data, schema=['id', 'value'])
        table_full_name = "{database}.{table}".format(database=database, table=table)
        df.writeTo(table_full_name).append()
    
    
    def main():
        # Creating a Spark session
        spark = (
            SparkSession
            .builder
            .appName('job_with_table')
            .enableHiveSupport()
            .getOrCreate()
        )
        database, table = 'database_1', 'table_1'
        prepare_table(spark, database, table)
        write_data(spark, database, table)
    
    
    if __name__ == '__main__':
        main()
    
    

  2. In <bucket_for_PySpark_job_source_code>, create a folder named scripts and upload the job_with_table.py file to it.

  1. Create a local file named job_with_table.py and paste the following script to it:

    import random
    from pyspark.sql import SparkSession
    
    
    def prepare_table(spark, database, table):
        create_database_sql = "create database if not exists {database}"
        create_table_sql = """
        create table if not exists {database}.{table} (
            id int,
            value double
        )
        using iceberg
        """
        truncate_table_sql = "truncate table {database}.{table}"
    
        spark.sql(create_database_sql.format(database=database))
        spark.sql(create_table_sql.format(database=database, table=table))
        spark.sql(truncate_table_sql.format(database=database, table=table))
    
    
    def write_data(spark, database, table):
        data = [(i, random.random()) for i in range(100_000)]
        # Creating a dataframe
        df = spark.createDataFrame(data, schema=['id', 'value'])
        table_full_name = "{database}.{table}".format(database=database, table=table)
        df.writeTo(table_full_name).append()
    
    
    def main():
        # Creating a Spark session
        spark = (
            SparkSession
            .builder
            .appName('job_with_table')
            .enableHiveSupport()
            .getOrCreate()
        )
        database, table = 'database_1', 'table_1'
        prepare_table(spark, database, table)
        write_data(spark, database, table)
    
    
    if __name__ == '__main__':
        main()
    
    

  2. In <bucket_for_jobs_and_data>, create a folder named scripts and upload the job_with_table.py file to it.

Prepare and run a DAG filePrepare and run a DAG file

A DAG will have multiple vertices that form a sequence of actions:

  1. Yandex Managed Service for Apache Airflow™ creates a temporary Apache Spark™ cluster with settings specified in the DAG. This cluster automatically connects to the previously created Apache Hive™ Metastore cluster.
  2. When the Apache Spark™ cluster is ready, a PySpark job is run.
  3. Once the job is complete, the temporary Apache Spark™ cluster is deleted.

To prepare a DAG:

High security level
Simplified setup
  1. Create a local file named dag.py, paste the following script to it and substitute the variables with your infrastructure data:

    dag.py
    import logging
    import pendulum
    from airflow.models.dag import DAG
    from airflow.decorators import task
    from airflow.providers.yandex.hooks.yandex import YandexCloudBaseHook
    
    from yandexcloud.operations import OperationError
    
    
    YANDEX_CONN_ID = '<connection_ID>'
    
    # Your infrastructure data
    FOLDER_ID = '<folder_ID>'
    SERVICE_ACCOUNT_ID = '<spark-agent_service_account_ID>'
    SUBNET_IDS = [<subnet_ID>]
    SECURITY_GROUP_IDS = [<security_group_ID>]
    METASTORE_CLUSTER_ID = '<Apache_Hive™_Metastore_cluster_ID>'
    
    JOB_NAME = 'job_with_table'
    JOB_SCRIPT = 's3a://<bucket_for_PySpark_job_source_code>/scripts/job_with_table.py'
    JOB_ARGS = []
    JOB_PROPERTIES = {
        'spark.executor.instances': '1',
        'spark.sql.warehouse.dir': 's3a://<bucket_for_PySpark_job_output_data>/warehouse',
    }
    
    
    @task
    # Step 1: Creating an Apache Spark™ cluster
    def create_cluster(yc_hook, cluster_spec):
        spark_client = yc_hook.sdk.wrappers.Spark()
        try:
            spark_client.create_cluster(cluster_spec)
        except OperationError as job_error:
            cluster_id = job_error.operation_result.meta.cluster_id
            if cluster_id:
                spark_client.delete_cluster(cluster_id=cluster_id)
            raise
        return spark_client.cluster_id
    
    
    @task
    # Step 2: Running a PySpark job
    def run_spark_job(yc_hook, cluster_id, job_spec):
        spark_client = yc_hook.sdk.wrappers.Spark()
        try:
            job_operation = spark_client.create_pyspark_job(cluster_id=cluster_id, spec=job_spec)
            job_id = job_operation.response.id
            job_info = job_operation.response
        except OperationError as job_error:
            job_id = job_error.operation_result.meta.job_id
            job_info, _ = spark_client.get_job(cluster_id=cluster_id, job_id=job_id)
            raise
        finally:
            job_log = spark_client.get_job_log(cluster_id=cluster_id, job_id=job_id)
            for line in job_log:
                logging.info(line)
            logging.info("Job info: %s", job_info)
    
    
    @task(trigger_rule="all_done")
    # Step 3: Deleting the Apache Spark™ cluster
    def delete_cluster(yc_hook, cluster_id):
        if cluster_id:
            spark_client = yc_hook.sdk.wrappers.Spark()
            spark_client.delete_cluster(cluster_id=cluster_id)
    
    
    # DAG settings
    with DAG(
        dag_id="example_spark",
        start_date=pendulum.datetime(2025, 1, 1),
        schedule=None,
    ):
        yc_hook = YandexCloudBaseHook(yandex_conn_id=YANDEX_CONN_ID)
    
        cluster_spec = yc_hook.sdk.wrappers.SparkClusterParameters(
            folder_id=FOLDER_ID,
            service_account_id=SERVICE_ACCOUNT_ID,
            subnet_ids=SUBNET_IDS,
            security_group_ids=SECURITY_GROUP_IDS,
            driver_pool_resource_preset="c2-m8",
            driver_pool_size=1,
            executor_pool_resource_preset="c4-m16",
            executor_pool_min_size=1,
            executor_pool_max_size=2,
            metastore_cluster_id=METASTORE_CLUSTER_ID,
        )
        cluster_id = create_cluster(yc_hook, cluster_spec)
    
        job_spec = yc_hook.sdk.wrappers.PysparkJobParameters(
            name=JOB_NAME,
            main_python_file_uri=JOB_SCRIPT,
            args=JOB_ARGS,
            properties=JOB_PROPERTIES,
        )
        task_job = run_spark_job(yc_hook, cluster_id, job_spec)
        task_delete = delete_cluster(yc_hook, cluster_id)
    
        task_job >> task_delete
    

    Where:

    • YANDEX_CONN_ID: Connection ID.

    • FOLDER_ID: ID of the folder you will create the Apache Spark™ cluster in.

    • SERVICE_ACCOUNT_ID: ID of the service account you will use to create the Apache Spark™ cluster.

    • SUBNET_IDS: Subnet ID.

      Note

      Apache Spark™ and Apache Hive™ Metastore must have the same subnet.

    • SECURITY_GROUP_IDS: ID of the security group for the Apache Spark™ cluster.

    • METASTORE_CLUSTER_ID: Apache Hive™ Metastore cluster ID.

    • JOB_NAME: PySpark job name.

    • JOB_SCRIPT: Path to the PySpark job file.

    • JOB_ARGS: PySpark job arguments.

    • JOB_PROPERTIES: PySpark job properties.

  2. Upload the DAG to the Apache Airflow™ cluster: in <bucket_for_Airflow_DAG_source_code>, create a folder named dags and upload the dag.py file to it.

  3. Open the Apache Airflow™ web interface.

  4. Make sure the new example_spark DAG has appeared in the DAGs section.

    It may take a few minutes to load a DAG file from the bucket.

  5. To run the DAG, click image in the line with its name.

  1. Create a local file named dag.py, paste the following script to it and substitute the variables with your infrastructure data:

    import logging
    import pendulum
    from airflow.models.dag import DAG
    from airflow.decorators import task
    from airflow.providers.yandex.hooks.yandex import YandexCloudBaseHook
    
    from yandexcloud.operations import OperationError
    
    
    YANDEX_CONN_ID = '<connection_ID>'
    
    # Your infrastructure data
    FOLDER_ID = '<folder_ID>'
    SERVICE_ACCOUNT_ID = '<integration-agent_service_account_ID>'
    SUBNET_IDS = [<subnet_ID>]
    SECURITY_GROUP_IDS = [<security_group_ID>]
    METASTORE_CLUSTER_ID = '<Apache_Hive™_Metastore_cluster_ID>'
    
    JOB_NAME = 'job_with_table'
    JOB_SCRIPT = 's3a://<bucket_for_jobs_and_data>/scripts/job_with_table.py'
    JOB_ARGS = []
    JOB_PROPERTIES = {
        'spark.executor.instances': '1',
        'spark.sql.warehouse.dir': 's3a://<bucket_for_jobs_and_data>/warehouse',
    }
    
    
    @task
    # Step 1: Creating an Apache Spark™ cluster
    def create_cluster(yc_hook, cluster_spec):
        spark_client = yc_hook.sdk.wrappers.Spark()
        try:
            spark_client.create_cluster(cluster_spec)
        except OperationError as job_error:
            cluster_id = job_error.operation_result.meta.cluster_id
            if cluster_id:
                spark_client.delete_cluster(cluster_id=cluster_id)
            raise
        return spark_client.cluster_id
    
    
    @task
    # Step 2: Running a PySpark job
    def run_spark_job(yc_hook, cluster_id, job_spec):
        spark_client = yc_hook.sdk.wrappers.Spark()
        try:
            job_operation = spark_client.create_pyspark_job(cluster_id=cluster_id, spec=job_spec)
            job_id = job_operation.response.id
            job_info = job_operation.response
        except OperationError as job_error:
            job_id = job_error.operation_result.meta.job_id
            job_info, _ = spark_client.get_job(cluster_id=cluster_id, job_id=job_id)
            raise
        finally:
            job_log = spark_client.get_job_log(cluster_id=cluster_id, job_id=job_id)
            for line in job_log:
                logging.info(line)
            logging.info("Job info: %s", job_info)
    
    
    @task(trigger_rule="all_done")
    # Step 3: Deleting the Apache Spark™ cluster
    def delete_cluster(yc_hook, cluster_id):
        if cluster_id:
            spark_client = yc_hook.sdk.wrappers.Spark()
            spark_client.delete_cluster(cluster_id=cluster_id)
    
    
    # DAG settings
    with DAG(
        dag_id="example_spark",
        start_date=pendulum.datetime(2025, 1, 1),
        schedule=None,
    ):
        yc_hook = YandexCloudBaseHook(yandex_conn_id=YANDEX_CONN_ID)
    
        cluster_spec = yc_hook.sdk.wrappers.SparkClusterParameters(
            folder_id=FOLDER_ID,
            service_account_id=SERVICE_ACCOUNT_ID,
            subnet_ids=SUBNET_IDS,
            security_group_ids=SECURITY_GROUP_IDS,
            driver_pool_resource_preset="c2-m8",
            driver_pool_size=1,
            executor_pool_resource_preset="c4-m16",
            executor_pool_min_size=1,
            executor_pool_max_size=2,
            metastore_cluster_id=METASTORE_CLUSTER_ID,
        )
        cluster_id = create_cluster(yc_hook, cluster_spec)
    
        job_spec = yc_hook.sdk.wrappers.PysparkJobParameters(
            name=JOB_NAME,
            main_python_file_uri=JOB_SCRIPT,
            args=JOB_ARGS,
            properties=JOB_PROPERTIES,
        )
        task_job = run_spark_job(yc_hook, cluster_id, job_spec)
        task_delete = delete_cluster(yc_hook, cluster_id)
    
        task_job >> task_delete
    

    Where:

    • YANDEX_CONN_ID: Connection ID.

    • FOLDER_ID: ID of the folder you will create the Apache Spark™ cluster in.

    • SERVICE_ACCOUNT_ID: ID of the service account you will use to create the Apache Spark™ cluster.

    • SUBNET_IDS: Subnet ID.

      Note

      Apache Spark™ and Apache Hive™ Metastore must have the same subnet.

    • SECURITY_GROUP_IDS: ID of the security group for the Apache Spark™ cluster.

    • METASTORE_CLUSTER_ID: Apache Hive™ Metastore cluster ID.

    • JOB_NAME: PySpark job name.

    • JOB_SCRIPT: Path to the PySpark job file.

    • JOB_ARGS: PySpark job arguments.

    • JOB_PROPERTIES: PySpark job properties.

  2. Upload the DAG to the Apache Airflow™ cluster: in <bucket_for_jobs_and_data>, create a folder named dags and upload the dag.py file to it.

  3. Open the Apache Airflow™ web interface.

  4. Make sure the new example_spark DAG has appeared in the DAGs section.

    It may take a few minutes to load a DAG file from the bucket.

  5. To run a DAG, click image in the line with its name.

Check the resultCheck the result

High security level
Simplified setup
  1. To monitor task execution results, click the DAG name.
  2. Wait until the status of all the three tasks in the DAG changes to Success. Simultaneously, you can check that an Apache Spark™ cluster is being created, the PySpark job is running, and the same cluster is being deleted in the management console.
  3. Make sure <bucket_for_PySpark_job_output_data> now contains database_1. The data from the new DB is now stored in the Object Storage bucket, and the DB metadata is stored in the Apache Hive™ Metastore cluster.
  1. To monitor task execution results, click the DAG name.
  2. Wait until the status of all the three tasks in the DAG changes to Success. Simultaneously, you can check that an Apache Spark™ cluster is being created, the PySpark job is running, and the same cluster is being deleted in the management console.
  3. Make sure <bucket_for_jobs_and_data> now contains database_1. The data from the new DB is now stored in the Object Storage bucket, and the DB metadata is stored in the Apache Hive™ Metastore cluster.

Delete the resources you createdDelete the resources you created

Some resources are not free of charge. Delete the resources you no longer need to avoid paying for them:

High security level
Simplified setup
  1. Service accounts.
  2. Object Storage buckets.
  3. Apache Hive™ Metastore cluster.
  4. Apache Airflow™ cluster.
  5. Security groups.
  6. Cloud subnets created in datalake-network by default.
  7. Cloud network.
  1. Service account.
  2. Object Storage bucket.
  3. Apache Hive™ Metastore cluster.
  4. Apache Airflow™ cluster.
  5. Security group created in datalake-network by default.
  6. Cloud subnets created in datalake-network by default.
  7. Cloud network.

Was the article helpful?

Previous
Creating a schema registry to deliver data in Debezium CDC format from Apache Kafka®
Next
Working with an Object Storage table from a PySpark job
© 2025 Direct Cursus Technology L.L.C.