Create an Apache Iceberg table with metadata in BigLake metastore

This document shows you how to create an Apache Iceberg table with metadata in BigLake metastore using the Dataproc Jobs service, the Spark SQL CLI or the Zeppelin web interface running on a Dataproc cluster.

Before you begin

If you haven't done so, create a Google Cloud project, a Cloud Storage bucket , and a Dataproc cluster.

Set up your project
Create a Cloud Storage bucket in your project.
1. In the Google Cloud console, go to the Cloud Storage Buckets page.
  Go to Buckets
2. Click Create .
3. On the Create a bucket page, enter your bucket information. To go to the next step, click Continue .
  1. In the Get started section, do the following:
    - Enter a globally unique name that meets the bucket naming requirements .
    - To add a bucket label , expand the Labels section ( ), click Add label , and specify a key and a value for your label.
  2. In the Choose where to store your data section, do the following:
    1. Select a Location type .
    2. Choose a location where your bucket's data is permanently stored from the Location type drop-down menu.
      - If you select the dual-region location type, you can also choose to enable turbo replication by using the relevant checkbox.
    3. To set up cross-bucket replication , select Add cross-bucket replication via Storage Transfer Service and follow these steps:
      Set up cross-bucket replication
      
      In the Bucket menu, select a bucket.
      
      In the Replication settings section, click Configure to configure settings for the replication job.
      
      The Configure cross-bucket replication pane appears.
      
      To filter objects to replicate by object name prefix, enter a prefix that you want to include or exclude objects from, then click Add a prefix .
      
      To set a storage class for the replicated objects, select a storage class from the Storage class menu. If you skip this step, the replicated objects will use the destination bucket's storage class by default.
      
      Click Done .
  3. In the Choose how to store your data section, do the following:
    1. Select a default storage class for the bucket or Autoclass for automatic storage class management of your bucket's data.
    2. To enable hierarchical namespace , in the Optimize storage for data-intensive workloads section, select Enable hierarchical namespace on this bucket .
      Note: You cannot enable hierarchical namespace in existing buckets.
  4. In the Choose how to control access to objects section, select whether or not your bucket enforces public access prevention , and select an access control method for your bucket's objects.
    Note: You cannot change the Prevent public access setting if this setting is enforced at an organization policy .
  5. In the Choose how to protect object data section, do the following:
    - Select any of the options under Data protection that you want to set for your bucket.
      - To enable soft delete , click the Soft delete policy (For data recovery) checkbox, and specify the number of days you want to retain objects after deletion.
      - To set Object Versioning , click the Object versioning (For version control) checkbox, and specify the maximum number of versions per object and the number of days after which the noncurrent versions expire.
      - To enable the retention policy on objects and buckets, click the Retention (For compliance) checkbox, and then do the following:
        
        To enable Object Retention Lock , click the Enable object retention checkbox.
        
        To enable Bucket Lock , click the Set bucket retention policy checkbox, and choose a unit of time and a length of time for your retention period.
    - To choose how your object data will be encrypted, expand the Data encryption section ( ), and select a Data encryption method .
4. Click Create .
Create a Dataproc cluster . To save resources and costs, you can create a single-node Dataproc cluster to run the examples presented in this document.
- The subnet in the region where the cluster is created must have Private Google Access (PGA) enabled.
  By default, Dataproc cluster VMs, created with a 2.2 (default) or later image version, have internal IP addresses only . To allow cluster VMs to communicate with Google APIs, enable Private Google Access on the default (or user-specified network name, if applicable) network subnet in the region where the cluster is created.
  .
- If you want to run the Zeppelin web interface example in this guide, you must use or create a Dataproc cluster with the Zeppelin optional component enabled .
Grant roles to a custom service account (if needed): By default, Dataproc cluster VMs use the Compute Engine default service account to interact with Dataproc. If you want to specify a custom service account when you create your cluster, it must have the Dataproc Worker role ( roles/dataproc.worker ) role or a custom role with needed Worker role permissions.

OSS database to BigQuery dataset mapping

Note the following mapping between open source database and BigQuery dataset terms:

OSS database	BigQuery dataset
Namespace, Database	Dataset
Partitioned or Unpartitioned Table	Table
View	View

Create an Iceberg table

This section shows you how to create an Iceberg table with metadata in BigLake metastore by submitting a Spark SQL code to the Dataproc service , the Spark SQL CLI , and the Zeppelin component web interface, which run on a Dataproc cluster.

Dataproc job

You can submit a job to the Dataproc service by submitting the job to a Dataproc cluster using the Google Cloud console or the Google Cloud CLI , or via a HTTP REST request or programmatic gRPC Dataproc Cloud Client Libraries call to the Dataproc Jobs API.

The examples in this section show you how to submit a Dataproc Spark SQL job to the Dataproc service to create an Iceberg table with metadata in BigQuery using the gcloud CLI, Google Cloud console, or Dataproc REST API.

Prepare job files

Perform the following steps to create a Spark SQL job file. The file contains Spark SQL commands to create and update an Iceberg table.

In a local terminal window or in Cloud Shell , use a text editor, such as the vi or nano , to copy the following commands into an iceberg-table.sql file, then save the file in the current directory.

USE CATALOG_NAME 
;
CREATE NAMESPACE IF NOT EXISTS example_namespace;
USE example_namespace;
DROP TABLE IF EXISTS example_table;
CREATE TABLE example_table (id int, data string) USING ICEBERG LOCATION 'gs:// BUCKET 
/ WAREHOUSE_FOLDER 
';
INSERT INTO example_table VALUES (1, 'first row');
ALTER TABLE example_table ADD COLUMNS (newDoubleCol double);
DESCRIBE TABLE example_table;

Replace the following:

CATALOG_NAME : Iceberg catalog name.
BUCKET and WAREHOUSE_FOLDER : Cloud Storage bucket and folder used for the Iceberg warehouse.

Use gcloud CLI to copy the local iceberg-table.sql to your bucket in Cloud Storage.
```
gcloud storage cp iceberg-table.sql gs:// BUCKET 
/
```

Next, download and copy the iceberg-spark-runtime-3.5_2.12-1.6.1 JAR file to Cloud Storage.

In a local terminal window or in Cloud Shell , run the following curl command to download the iceberg-spark-runtime-3.5_2.12-1.6.1 JAR file to the current directory.

curl -o iceberg-spark-runtime-3.5_2.12-1.6.1.jar https://storage-download.googleapis.com/maven-central/maven2/org/apache/iceberg/iceberg-spark-runtime-3.5_2.12/1.6.1/iceberg-spark-runtime-3.5_2.12-1.6.1.jar

Uses the gcloud CLI to copy the local iceberg-spark-runtime-3.5_2.12-1.6.1 JAR file from the current directory to your bucket in Cloud Storage.
```
gcloud storage cp iceberg-spark-runtime-3.5_2.12-1.6.1.jar gs:// BUCKET 
/
```

Submit the Spark SQL job

Select a tab to follow the instructions to submit the Spark SQL job to the Dataproc service using the gcloud CLI, Google Cloud console, or Dataproc REST API.

gcloud

Run the following gcloud dataproc jobs submit spark-sql command locally in a local terminal window or in Cloud Shell to submit the Spark SQL job to create the Iceberg table.
```
gcloud dataproc jobs submit spark-sql \
    --project= PROJECT_ID 
\
    --cluster= CLUSTER_NAME 
\
    --region= REGION 
\
    --jars="gs:// BUCKET 
/1.6.1/iceberg-spark-runtime-3.5_2.12-1.6.1.jar,gs://spark-lib/bigquery/iceberg-bigquery-catalog-1.6.1-1.0.1-beta.jar" \
    --properties="spark.sql.catalog. CATALOG_NAME 
=org.apache.iceberg.spark.SparkCatalog,spark.sql.catalog. CATALOG_NAME 
.catalog-impl=org.apache.iceberg.gcp.bigquery.BigQueryMetastoreCatalog,spark.sql.catalog. CATALOG_NAME 
.gcp_project= PROJECT_ID 
,spark.sql.catalog. CATALOG_NAME 
.gcp_location= LOCATION 
,spark.sql.catalog. CATALOG_NAME 
.warehouse=gs:// BUCKET 
/ WAREHOUSE_FOLDER 
" \
    -f="gs:// BUCKET 
iceberg-table.sql"
```
Notes:
- PROJECT_ID : Your Google Cloud project ID. Project IDs are listed in the Project infosection on the Google Cloud console Dashboard .
- CLUSTER_NAME : The name of your Dataproc cluster.
- REGION : The Compute Engine region where your cluster is located.
- CATALOG_NAME : Iceberg catalog name.
- BUCKET and WAREHOUSE_FOLDER : Cloud Storage bucket and folder used for the Iceberg warehouse.
- LOCATION : A supported BigQuery location . The default location is "US".
- --jars : The listed jars are necessary to create table metadata in BigLake metastore.
- --properties : Catalog properties .
- -f : The iceberg-table.sql job file you copied to your bucket in Cloud Storage.

View the table description in the terminal output when the job finishes.

Time taken: 2.194 seconds
id                      int
data                    string
newDoubleCol            double
Time taken: 1.479 seconds, Fetched 3 row(s)
Job JOB_ID 
finished successfully.

To view table metadata in BigQuery
1. In the Google Cloud console, go to the BigQuerypage.
  
  Go to BigQuery Studio
2. View Iceberg table metadata.

Console

Perform the following steps to use the Google Cloud console to submit the Spark SQL job to the Dataproc service to create an Iceberg table with metadata in BigLake metastore.

In the Google Cloud console, go to the Dataproc Submit a job.

Go to Submit a job page, then complete the following fields:

Job ID: Accept the suggested ID or insert your own ID.
Region: Select the region where your cluster is located.
Cluster: Select your cluster.
Job type: Select SparkSql .
Query source type: Select Query file .
Query file: Insert gs:// BUCKET /iceberg-table.sql

Jar files: Insert the following:

gs:// BUCKET 
/iceberg-spark-runtime-3.5_2.12-1.6.1.jar,gs://spark-lib/bigquery/iceberg-bigquery-catalog-1.6.1-1.0.1-beta.jar

Properties: Click Add Propertyfive times to create a list of five key value input fields, then copy the following Keyand Valuepairs to define five properties.

#	Key	Value
1.	`spark.sql.catalog. CATALOG_NAME`	`org.apache.iceberg.spark.SparkCatalog`
2.	`spark.sql.catalog. CATALOG_NAME .catalog-impl`	`org.apache.iceberg.gcp.bigquery.BigQueryMetastoreCatalog`
3.	`spark.sql.catalog. CATALOG_NAME .gcp_project`	`PROJECT_ID`
4.	`spark.sql.catalog. CATALOG_NAME .gcp_location`	`LOCATION`
5.	`spark.sql.catalog. CATALOG_NAME .warehouse`	`gs:// BUCKET / WAREHOUSE_FOLDER`

Notes:

CATALOG_NAME : Iceberg catalog name.
PROJECT_ID : Your Google Cloud project ID. Project IDs are listed in the Project infosection on the Google Cloud console Dashboard . region where your cluster is located.
LOCATION : A supported BigQuery location . The default location is "US".
BUCKET and WAREHOUSE_FOLDER : Cloud Storage bucket and folder used for the Iceberg warehouse.

Click Submit
To monitor job progress and view job output, go to the Dataproc Jobs page in the Google Cloud console, then click the Job ID to open the Job detailspage.
To view table metadata in BigQuery
1. In the Google Cloud console, go to the BigQuerypage.
  
  Go to BigQuery Studio
2. View Iceberg table metadata.

REST

You can use the Dataproc jobs.submit API to submit the Spark SQL job to the Dataproc service to create an Iceberg table with metadata in BigLake metastore.

Before using any of the request data, make the following replacements:

PROJECT_ID : Your Google Cloud project ID. Project IDs are listed in the Project infosection on the Google Cloud console Dashboard .
CLUSTER_NAME : The name of your Dataproc cluster.
REGION : The Compute Engine region where your cluster is located.
CATALOG_NAME : Iceberg catalog name.
BUCKET and WAREHOUSE_FOLDER : Cloud Storage bucket and folder used for the Iceberg warehouse.

LOCATION

: A supported

BigQuery location

. The default location is "US".

jarFileUris : The listed jars are necessary to create table metadata in BigQuery Metastore.
properties : Catalog properties .
queryFileUri : The iceberg-table.sql job file you copied to your bucket in Cloud Storage.

HTTP method and URL:

POST https://dataproc.googleapis.com/v1/projects/ PROJECT_ID 
/regions/ REGION 
/jobs:submit

Request JSON body:

{
  "projectId": " PROJECT_ID 
",
  "job": {
    "placement": {
      "clusterName": " CLUSTER_NAME 
"
    },
    "statusHistory": [],
    "reference": {
      "jobId": "",
      "projectId": " PROJECT_ID 
"
    },
    "sparkSqlJob": {
      "properties": {
        "spark.sql.catalog." CATALOG_NAME 
": "org.apache.iceberg.spark.SparkCatalog",
        "spark.sql.catalog." CATALOG_NAME 
".catalog-impl": "org.apache.iceberg.gcp.bigquery.BigQueryMetastoreCatalog",
        "spark.sql.catalog." CATALOG_NAME 
".gcp_project": " PROJECT_ID 
",
        "spark.sql.catalog." CATALOG_NAME 
".gcp_location": " LOCATION 
",
        "spark.sql.catalog." CATALOG_NAME 
".warehouse": "gs:// BUCKET 
/ WAREHOUSE_FOLDER 
"
      },
      "jarFileUris": [
        "gs:// BUCKET 
/iceberg-spark-runtime-3.5_2.12-1.5.2.jar,gs://spark-lib/bigquery/iceberg-bigquery-catalog-1.5.2-1.0.1-beta.jar"
      ],
      "scriptVariables": {},
      "queryFileUri": "gs:// BUCKET 
/iceberg-table.sql"
    }
  }
}

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Note: The following command assumes that you have logged in to the gcloud CLI with your user account by running gcloud init or gcloud auth login , or by using Cloud Shell , which automatically logs you into the gcloud CLI . You can check the currently active account by running gcloud auth list .

Save the request body in a file named request.json , and execute the following command:

curl -X POST \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
-H "Content-Type: application/json; charset=utf-8" \
-d @request.json \
"https://dataproc.googleapis.com/v1/projects/ PROJECT_ID 
/regions/ REGION 
/jobs:submit"

PowerShell (Windows)

Note: The following command assumes that you have logged in to the gcloud CLI with your user account by running gcloud init or gcloud auth login . You can check the currently active account by running gcloud auth list .

Save the request body in a file named request.json , and execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
-Method POST `
-Headers $headers `
-ContentType: "application/json; charset=utf-8" `
-InFile request.json `
-Uri "https://dataproc.googleapis.com/v1/projects/ PROJECT_ID 
/regions/ REGION 
/jobs:submit" | Select-Object -Expand Content

You should receive a JSON response similar to the following:

{
  "reference": {
    "projectId": " PROJECT_ID 
",
    "jobId": "..."
  },
  "placement": {
    "clusterName": " CLUSTER_NAME 
",
    "clusterUuid": "..."
  },
  "status": {
    "state": "PENDING",
    "stateStartTime": "..."
  },
  "submittedBy": " USER 
",
  "sparkSqlJob": {
    "queryFileUri": "gs:// BUCKET 
/iceberg-table.sql",
    "properties": {
      "spark.sql.catalog. USER 
_catalog": "org.apache.iceberg.spark.SparkCatalog",
      "spark.sql.catalog. USER 
_catalog.catalog-impl": "org.apache.iceberg.gcp.bigquery.BigQueryMetastoreCatalog",
      "spark.sql.catalog. USER 
_catalog.gcp_project": " PROJECT_ID 
",
      "spark.sql.catalog. USER 
_catalog.gcp_location": " LOCATION 
",
      "spark.sql.catalog. USER 
_catalog.warehouse": "gs:// BUCKET 
/ WAREHOUSE_FOLDER 
"
    },
    "jarFileUris": [
      "gs:// BUCKET 
/iceberg-spark-runtime-3.5_2.12-1.5.2.jar",
      "gs://spark-lib/bigquery/iceberg-bigquery-catalog-1.5.2-1.0.1-beta.jar"
    ]
  },
  "driverControlFilesUri": "gs://dataproc-...",
  "driverOutputResourceUri": "gs://dataproc-.../driveroutput",
  "jobUuid": "...",
  "region": " REGION 
"
}

To monitor job progress and view job output, go to the Dataproc Jobs page in the Google Cloud console, then click the Job ID to open the Job detailspage.

To view table metadata in BigQuery

In the Google Cloud console, go to the BigQuerypage.

Go to BigQuery Studio
View Iceberg table metadata.

Spark SQL CLI

The following steps show you how to create an Iceberg table with table metadata stored in BigLake metastore using the Spark SQL CLI running on the master node of a Dataproc cluster.

Use SSH to connect to the master node of your Dataproc cluster.

In the SSH session terminal, use the vi or nano text editor to copy the following commands into an iceberg-table.sql file.

SET CATALOG_NAME = ` CATALOG_NAME 
`;
SET BUCKET = ` BUCKET 
`;
SET WAREHOUSE_FOLDER = ` WAREHOUSE_FOLDER 
`;
USE `${CATALOG_NAME}`;
CREATE NAMESPACE IF NOT EXISTS `${CATALOG_NAME}`.example_namespace;
DROP TABLE IF EXISTS `${CATALOG_NAME}`.example_namespace.example_table;
CREATE TABLE `${CATALOG_NAME}`.example_namespace.example_table (id int, data string) USING ICEBERG LOCATION 'gs://${BUCKET}/${WAREHOUSE_FOLDER}';
INSERT INTO `${CATALOG_NAME}`.example_namespace.example_table VALUES (1, 'first row');
ALTER TABLE `${CATALOG_NAME}`.example_namespace.example_table ADD COLUMNS (newDoubleCol double);
DESCRIBE TABLE `${CATALOG_NAME}`.example_namespace.example_table;

Replace the following:

CATALOG_NAME : Iceberg catalog name.
BUCKET and WAREHOUSE_FOLDER : Cloud Storage bucket and folder used for the Iceberg warehouse.

In the SSH session terminal, run the following spark-sql command to create the iceberg table.

spark-sql \
--packages org.apache.iceberg:iceberg-spark-runtime-3.5_2.12:1.6.1 \
--jars https://storage-download.googleapis.com/maven-central/maven2/org/apache/iceberg/iceberg-spark-runtime-3.5_2.12/1.6.1/iceberg-spark-runtime-3.5_2.12-1.6.1.jar,gs://spark-lib/bigquery/iceberg-bigquery-catalog-1.6.1-1.0.1-beta.jar \
--conf spark.sql.catalog. CATALOG_NAME 
=org.apache.iceberg.spark.SparkCatalog \
--conf spark.sql.catalog. CATALOG_NAME 
.catalog-impl=org.apache.iceberg.gcp.bigquery.BigQueryMetastoreCatalog \
--conf spark.sql.catalog. CATALOG_NAME 
.gcp_project= PROJECT_ID 
\
--conf spark.sql.catalog. CATALOG_NAME 
.gcp_location= LOCATION 
\
--conf spark.sql.catalog. CATALOG_NAME 
.warehouse=gs:// BUCKET 
/ WAREHOUSE_FOLDER 
\
-f iceberg-table.sql

Replace the following:

PROJECT_ID : Your Google Cloud project ID. Project IDs are listed in the Project infosection on the Google Cloud console Dashboard .
LOCATION : A supported BigQuery location . The default location is "US".

View table metadata in BigQuery
1. In the Google Cloud console, go to the BigQuerypage.
  
  Go to BigQuery Studio
2. View Iceberg table metadata.

Zeppelin web interface

The following steps show you how to to create an Iceberg table with table metadata stored in BigLake metastore using the Zeppelin web interface running on the master node of a Dataproc cluster .

In the Google Cloud console, go to the Dataproc Clusterspage.

Go to the Dataproc Clusters page
Select your cluster name to open the Cluster detailspage.
Click the Web Interfacestab display a list of Component Gatewaylinks to the web interfaces of default and optional components installed on the cluster.
Click the Zeppelinlink to open the Zeppelin web interface.
In the Zeppelin web interface, click the anonymousmenu, then click Interpreterto open the Interpreterspage.
Add two jars to the Zeppelin Spark interpreter, as follows:
1. Type "Spark" in Search interpreters box to scroll to the Sparkinterpreter section.
2. Click edit.
3. Paste the following in the spark.jarsfield:
```
https://storage-download.googleapis.com/maven-central/maven2/org/apache/iceberg/iceberg-spark-runtime-3.5_2.12/1.6.1/iceberg-spark-runtime-3.5_2.12-1.6.1.jar,gs://spark-lib/bigquery/iceberg-bigquery-catalog-1.6.1-1.0.1-beta.jar
```
4. Click Saveat the bottom of the Spark interpreter section, then click OKto update the interpreter and restart the Spark interpreter with the new settings.
From the Zeppelin notebook menu, click Create new note.
In the Create new notedialog, input a name for the notebook, and accept the default sparkinterpreter. Click Createto open The notebook.

Copy the following PySpark code into your Zeppelin notebook after filling in the variables.

%pyspark
from  
pyspark.sql  
import  
SparkSession
 project_id 
  
 = 
  
 " PROJECT_ID 
" 
 catalog 
  
 = 
  
 " CATALOG_NAME 
" 
 namespace 
  
 = 
  
 " NAMESPACE 
" 
 location 
  
 = 
  
 " LOCATION 
" 
 warehouse_dir 
  
 = 
  
 "gs:// BUCKET 
/ WAREHOUSE_DIRECTORY 
" 

 spark 
  
 = 
  
SparkSession.builder  
 \ 
.appName ( 
 "BigQuery Metastore Iceberg" 
 ) 
  
 \ 
.config ( 
f "spark.sql.catalog.{catalog}" 
,  
 "org.apache.iceberg.spark.SparkCatalog" 
 ) 
  
 \ 
.config ( 
f "spark.sql.catalog.{catalog}.catalog-impl" 
,  
 "org.apache.iceberg.gcp.bigquery.BigQueryMetastoreCatalog" 
 ) 
  
 \ 
.config ( 
f "spark.sql.catalog.{catalog}.gcp_project" 
,  
f "{project_id}" 
 ) 
  
 \ 
.config ( 
f "spark.sql.catalog.{catalog}.gcp_location" 
,  
f "{location}" 
 ) 
  
 \ 
.config ( 
f "spark.sql.catalog.{catalog}.warehouse" 
,  
f "{warehouse_dir}" 
 ) 
  
 \ 
.getOrCreate () 

spark.sql ( 
f "USE `{catalog}`;" 
 ) 
spark.sql ( 
f "CREATE NAMESPACE IF NOT EXISTS `{namespace}`;" 
 ) 
spark.sql ( 
f "USE `{namespace}`;" 
 ) 

 \# 
  
Create  
table  
and  
display  
schema  
 ( 
without  
LOCATION ) 
spark.sql ( 
 "DROP TABLE IF EXISTS example_iceberg_table" 
 ) 
spark.sql ( 
 "CREATE TABLE example_iceberg_table (id int, data string) USING ICEBERG" 
 ) 
spark.sql ( 
 "DESCRIBE example_iceberg_table;" 
 ) 

 \# 
  
Insert  
table  
data.
spark.sql ( 
 "INSERT INTO example_iceberg_table VALUES (1, 'first row');" 
 ) 

 \# 
  
Alter  
table,  
 then 
  
display  
schema.
spark.sql ( 
 "ALTER TABLE example_iceberg_table ADD COLUMNS (newDoubleCol double);" 
 ) 

 \# 
  
Select  
and  
display  
the  
contents  
of  
the  
table.
spark.sql ( 
 "SELECT * FROM example_iceberg_table" 
 ) 
.show ()

Replace the following:

PROJECT_ID : Your Google Cloud project ID. Project IDs are listed in the Project infosection on the Google Cloud console Dashboard .
CATALOG_NAME and NAMESPACE : The Iceberg catalog name and namespace combine to identify the Iceberg table ( catalog.namespace.table_name ).
LOCATION : A supported BigQuery location . The default location is "US".
BUCKET and WAREHOUSE_DIRECTORY : Cloud Storage bucket and folder used as Iceberg warehouse directory.

Click the run icon or press Shift-Enter to run the code. When the job completes, the status message shows "Spark Job Finished", and the output displays the table contents:
View table metadata in BigQuery
1. In the Google Cloud console, go to the BigQuerypage.
  
  Go to BigQuery Studio
2. View Iceberg table metadata.

Create an Apache Iceberg table with metadata in BigLake metastore Stay organized with collections Save and categorize content based on your preferences.

Before you begin

Set up cross-bucket replication

OSS database to BigQuery dataset mapping

Create an Iceberg table

Dataproc job

Prepare job files

Submit the Spark SQL job

gcloud

Console

REST

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Spark SQL CLI

Zeppelin web interface

Create an Apache Iceberg table with metadata in BigLake metastore