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
  • Getting started
  • Connect Yandex Data Processing to Apache Hive™ Metastore
  • Create a test table
  • Get data in the second cluster
  • Delete the resources you created
  1. Building a data platform
  2. Shared use of Yandex Data Processing tables through Apache Hive™ Metastore

Shared use of Yandex Data Processing tables through Apache Hive™ Metastore

Written by
Yandex Cloud
Updated at December 3, 2025
  • Required paid resources
  • Getting started
  • Connect Yandex Data Processing to Apache Hive™ Metastore
  • Create a test table
  • Get data in the second cluster
  • Delete the resources you created

You can save data from a Yandex Data Processing cluster to a Yandex Object Storage bucket using a separate Apache Hive™ Metastore cluster to store table metadata. Thus you can access the saved data from a different Yandex Data Processing cluster that has access to the bucket and is connected to the same Apache Hive™ Metastore cluster.

To set up shared use of tables by two Yandex Data Processing clusters through Apache Hive™ Metastore:

  1. Connect Yandex Data Processing to Apache Hive™ Metastore.
  2. Create a test table.
  3. Get data in the second cluster.

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

If a Yandex Data Processing cluster contains tables that should be available in another Yandex Data Processing cluster, transfer the tables to the appropriate cluster using Apache Hive™ Metastore.

Warning

If you want to configure an access policy for a bucket and connect to it from a Apache Hive™ Metastore cluster, you will need some additional infrastructure setup. For more information, see this guide.

Required paid resourcesRequired paid resources

The infrastructure support cost includes:

  • Fee for the Yandex Data Processing cluster computing resources and storage (see Yandex Data Processing pricing).
  • Fee for the Apache Hive™ Metastore cluster computing resources (see Yandex MetaData Hub pricing).
  • Fee for data storage and operations in a bucket (see Yandex Object Storage pricing).
  • Fee for NAT gateway usage and outbound traffic (see Yandex Virtual Private Cloud pricing).

Getting startedGetting started

Set up the infrastructure:

Manually
Terraform
  1. Create a service account named dataproc-s3-sa and assign the dataproc.agent and dataproc.provisioner roles to it.

  2. In Object Storage, create buckets and configure access to them:

    1. Create a bucket for the input data and grant the READ permission for this bucket to the cluster service account.
    2. Create a bucket for the processing output and grant the cluster service account READ and WRITE permissions for this bucket.
  3. Create a cloud network named dataproc-network.

  4. In dataproc-network, create a subnet in any availability zone.

  5. Set up a NAT gateway for the subnet you created.

  6. Create two Yandex Data Processing clusters named dataproc-source and dataproc-target in any suitable host configuration with the following settings:

    • Environment: PRODUCTION.
    • Services:
      • SPARK
      • YARN
    • Service account: dataproc-sa.
    • Properties: spark:spark.sql.hive.metastore.sharedPrefixes with the com.amazonaws,ru.yandex.cloud value. It is required for PySpark jobs and integration with Apache Hive™ Metastore.
    • Bucket name: Bucket you created for output data.
    • Network: dataproc-network.
  7. If the cloud network uses security groups, add the following rule for outgoing traffic to the Yandex Data Processing cluster security group:

    • Port range: 9083
    • Protocol: Any (Any)
    • Source: CIDR
    • CIDR blocks: 0.0.0.0/0
  1. If you do not have Terraform yet, install it.

  2. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

  3. Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it.

  4. Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.

  5. Download the dataproc-to-dataproc.tf configuration file to the same working directory.

    This file describes:

    • Network.
    • Subnet.
    • NAT gateway and route table required for Yandex Data Processing.
    • Security groups for the Yandex Data Processing clusters.
    • Service account for the Yandex Data Processing cluster.
    • Service account required to create buckets in Object Storage.
    • Buckets for input and output data.
    • Two Yandex Data Processing clusters.
  6. Specify the following in dataproc-to-dataproc.tf:

    • folder_id: Cloud folder ID, same as in the provider settings.
    • input-bucket: Input data bucket name.
    • output-bucket: Output data bucket name.
    • dp_ssh_key: Absolute path to the public key for the Yandex Data Processing clusters. Learn more about connecting to a Yandex Data Processing host over SSH here.
  7. Make sure the Terraform configuration files are correct using this command:

    terraform validate
    

    Terraform will show any errors found in your configuration files.

  8. Create the required infrastructure:

    1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

    All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

Connect Yandex Data Processing to Apache Hive™ MetastoreConnect Yandex Data Processing to Apache Hive™ Metastore

  1. Create a Apache Hive™ Metastore cluster version 3.1 in dataproc-network.

  2. Add the spark:spark.hive.metastore.uris property with the thrift://<Apache Hive™ Metastore_cluster_IP_address>:9083 value to the Yandex Data Processing cluster settings.

    To find out the Apache Hive™ Metastore cluster IP address, select Yandex MetaData Hub in the management console and then select the Metastore page in the left-hand panel. Copy the IP address column value for the cluster in question.

Create a test tableCreate a test table

In the dataproc-source cluster, create a test table named countries and upload it to Object Storage:

Spark
  1. Prepare a script file:

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

      create-table.py
      from pyspark.sql.types import *
      from pyspark.sql import SparkSession
      
      # Creating a Spark session
      spark = SparkSession.builder \
          .appName("create-table") \
          .enableHiveSupport() \
          .getOrCreate()
      
      # Creating a data schema
      schema = StructType([StructField('Name', StringType(), True),
      StructField('Capital', StringType(), True),
      StructField('Area', IntegerType(), True),
      StructField('Population', IntegerType(), True)])
      
      # Creating a dataframe
      df = spark.createDataFrame([('Australia', 'Canberra', 7686850, 19731984), ('Austria', 'Vienna', 83855, 7700000)], schema)
      
      # Writing the dataframe to a bucket as a countries table
      df.write.mode("overwrite").option("path","s3a://<output_bucket_name>/countries").saveAsTable("countries")
      
    2. In the script, specify the name of the output bucket where the file with the countries table will be saved.

    3. In the input bucket, create a folder named scripts and upload the create-table.py file to it.

  2. Create a PySpark job by specifying the path to the script file in the Main python file field: s3a://<input_bucket_name>/scripts/create-table.py.

  3. Wait for the job to complete and make sure the output bucket's countries folder contains the part-00000-... file.

The data from the created table is now stored in the Object Storage bucket and the table metadata is stored in the Apache Hive™ Metastore cluster. Now you can delete the dataproc-source cluster.

Get data in the second clusterGet data in the second cluster

Upload the countries table metadata to the dataproc-target cluster and make sure the table is accessible in the cluster for further operations:

Spark
  1. Prepare a script file:

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

      obtain-table.py
      from pyspark.sql import SparkSession
      
      # Creating a Spark session
      spark = SparkSession.builder \
          .appName("obtain-table") \
          .enableHiveSupport() \
          .getOrCreate()
      
      spark.catalog.listDatabases()
      
      # Getting the `countries` table metadata from Apache Hive™ Metastore
      df = spark.sql("describe extended countries")
      
      # Requesting data from the countries table
      df = spark.sql("select * from countries")
      
      # Testing table-to-bucket transfer
      df.repartition(1).write.csv(path='s3a://<output_bucket_name>/csv', header=True, sep=',')
      
    2. In the script, specify the name of the output bucket where the CSV file with the countries table will be saved.

    3. Upload the obtain-table.py file to the input data bucket’s scripts folder.

  2. Create a PySpark job by specifying the path to the script file in the Main python file field: s3a://<input_bucket_name>/scripts/obtain-table.py.

  3. Wait for the job to complete and make sure the output bucket contains the csv folder with a table in CSV format.

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:

  1. Delete the Apache Hive™ Metastore cluster.

  2. Delete the objects from the buckets.

  3. Delete other resources depending on how they were created:

    Manually
    Terraform
    1. Yandex Data Processing clusters.
    2. Object Storage buckets.
    3. Subnet.
    4. Route table.
    5. NAT gateway.
    6. Cloud network.
    7. Service account.
    1. In the terminal window, go to the directory containing the infrastructure plan.

      Warning

      Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

    2. Delete resources:

      1. Run this command:

        terraform destroy
        
      2. Confirm deleting the resources and wait for the operation to complete.

      All the resources described in the Terraform manifests will be deleted.

Apache® and Apache Hive™ are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.

Was the article helpful?

Previous
Automating operations with Yandex Data Processing using Managed Service for Apache Airflow™
Next
Transferring metadata across Yandex Data Processing clusters using Apache Hive™ Metastore
© 2025 Direct Cursus Technology L.L.C.