Shared use of tables through Apache Hive™ Metastore
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:
- Connect Yandex Data Processing to Apache Hive™ Metastore.
- Create a test table.
- 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 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 started
Set up the infrastructure:
-
Create a service account named
dataproc-s3-saand assign thedataproc.agentanddataproc.provisionerroles to it. -
In Object Storage, create buckets and configure access to them:
- Create a bucket for the input data and grant the
READpermission for this bucket to the cluster service account. - Create a bucket for the processing output and grant the cluster service account
READ and WRITEpermissions for this bucket.
- Create a bucket for the input data and grant the
-
Create a cloud network named
dataproc-network. -
In
dataproc-network, create a subnet in any availability zone. -
Set up a NAT gateway for the subnet you created.
-
Create two Yandex Data Processing clusters named
dataproc-sourceanddataproc-targetin any suitable host configuration with the following settings:- Environment:
PRODUCTION. - Services:
SPARKYARN
- Service account:
dataproc-sa. - Properties:
spark:spark.sql.hive.metastore.sharedPrefixeswith thecom.amazonaws,ru.yandex.cloudvalue. It is required for PySpark jobs and integration with Apache Hive™ Metastore. - Bucket name: Bucket you created for output data.
- Network:
dataproc-network.
- Environment:
-
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
- Port range:
-
If you do not have Terraform yet, install it.
-
Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.
-
Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it
. -
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.
-
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.
-
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.
-
Validate your Terraform configuration files using this command:
terraform validateTerraform will display any configuration errors detected in your files.
-
Create the required infrastructure:
-
Run this command to view the planned changes:
terraform planIf 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.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
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™ Metastore
-
Create a Apache Hive™ Metastore cluster in
dataproc-network. -
Add the
spark:spark.hive.metastore.urisproperty with thethrift://<Apache Hive™ Metastore_cluster_IP_address>:9083value 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 table
In the dataproc-source cluster, create a test table named countries and upload it to Object Storage:
-
Prepare a script file:
-
Create a local file named
create-table.pyand 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") -
In the script, specify the name of the output bucket where the file with the
countriestable will be saved. -
Create a folder named
scriptsin the input bucket and upload thecreate-table.pyfile to it.
-
-
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. -
Wait for the job to complete and make sure the output bucket's
countriesfolder contains thepart-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 cluster
Upload the countries table metadata to the dataproc-target cluster and make sure the table is accessible in the cluster for further operations:
-
Prepare a script file:
-
Create a local file named
obtain-table.pyand 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=',') -
In the script, specify the name of the output bucket where the CSV file with the
countriestable will be saved. -
Upload the
obtain-table.pyfile to the input data bucket’sscriptsfolder.
-
-
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. -
Wait for the job to complete and make sure the output bucket contains the
csvfolder with a table in CSV format.
Delete the resources you created
Some resources are not free of charge. Delete the resources you no longer need to avoid paying for them:
-
Delete the objects from the buckets.
-
Delete other resources depending on how they were created:
ManuallyTerraform-
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.
-
Delete resources:
-
Run this command:
terraform destroy -
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™