Use BigLake metastore with Spark and BigQuery using the Iceberg REST catalog
Learn how to create a BigLake Iceberg table by running a Managed Service for Apache Spark PySpark job that connects to a BigLake metastore catalog using the Iceberg REST catalog.
After, you can query the resulting table directly from the Google Cloud console in
BigQuery with the project.catalog.namespace.table syntax.
Before you begin
- Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
Roles required to select or create a project
- Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
-
Create a project: To create a project, you need the Project Creator role
(
roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.createpermission. Learn how to grant roles.
-
Verify that billing is enabled for your Google Cloud project.
Enable the BigLake,Managed Service for Apache Spark APIs.
Roles required to enable APIs
To enable APIs, you need the Service Usage Admin IAM role (
roles/serviceusage.serviceUsageAdmin), which contains theserviceusage.services.enablepermission. Learn how to grant roles.-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
Roles required to select or create a project
- Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
-
Create a project: To create a project, you need the Project Creator role
(
roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.createpermission. Learn how to grant roles.
-
Verify that billing is enabled for your Google Cloud project.
Enable the BigLake,Managed Service for Apache Spark APIs.
Roles required to enable APIs
To enable APIs, you need the Service Usage Admin IAM role (
roles/serviceusage.serviceUsageAdmin), which contains theserviceusage.services.enablepermission. Learn how to grant roles.
Grant IAM roles
To allow the Spark job to interact with BigLake and BigQuery, grant the required Identity and Access Management (IAM) roles to the Compute Engine default service account.
In the Google Cloud console, click Activate Cloud Shell.
Click Authorize.
Grant the Managed Service for Apache Spark Worker role to the Compute Engine default service account, which Managed Service for Apache Spark uses by default.
gcloud projects add-iam-policy-binding PROJECT_ID \ --member="serviceAccount:$(gcloud projects describe PROJECT_ID --format='value(projectNumber)')-compute@developer.gserviceaccount.com" \ --role="roles/dataproc.worker"Grant the Service Usage Consumer role to the Compute Engine default service account.
gcloud projects add-iam-policy-binding PROJECT_ID \ --member="serviceAccount:$(gcloud projects describe PROJECT_ID --format='value(projectNumber)')-compute@developer.gserviceaccount.com" \ --role="roles/serviceusage.serviceUsageConsumer"Grant the BigLake Data Editor role to the Compute Engine default service account.
gcloud projects add-iam-policy-binding PROJECT_ID \ --member="serviceAccount:$(gcloud projects describe PROJECT_ID --format='value(projectNumber)')-compute@developer.gserviceaccount.com" \ --role="roles/biglake.editor"Grant the BigQuery Data Editor role to the Compute Engine default service account.
gcloud projects add-iam-policy-binding PROJECT_ID \ --member="serviceAccount:$(gcloud projects describe PROJECT_ID --format='value(projectNumber)')-compute@developer.gserviceaccount.com" \ --role="roles/bigquery.dataEditor"Replace the following:
PROJECT_ID: Your Google Cloud project ID.
Create a BigLake catalog
Create a BigLake catalog to manage metadata for your Iceberg tables. You connect to this catalog in your Spark job.
In the Google Cloud console, go to BigLake.
Click Create catalog.
The Create catalog page opens.
For Select a Cloud Storage bucket, click Browse, and then click Create new bucket.
Enter a unique name for your bucket.
Important
Remember the name of your bucket. It is also automatically used as your BigLake catalog name. It can't be changed. You can add this name here now, if you want to store the name in the variable to use later in this tutorial.
BIGLAKE_CATALOG_ID
Remember the region you create your bucket in. You must use the same region later in this tutorial when you run your Spark job with the
dataproc batches submit pysparkcommand. You can add this name here now, if you want to store the name in the variable to use later in this tutorial.REGION
From the bucket list, select your bucket and click Select.
For Authentication method, select Credential vending mode.
Click Create.
Your catalog is created and the Catalog details page opens.
Under Authentication method, click Set bucket permissions.
In the dialog, click Confirm.
This verifies that your catalog's service account has the Storage Object User role on your storage bucket.
Create and run a Spark job
To create and query an Iceberg table, first create a PySpark job with the necessary Spark SQL statements. Then run the job with Managed Service for Apache Spark.
Create a PySpark script with a namespace and table
In a text editor, create a file named quickstart.py with the following
content.
This PySpark script initializes a Spark session to perform several operations on
an Iceberg catalog. The script first creates a namespace, if one doesn't already
exist. It then creates an Iceberg table named quickstart_table
with a basic schema. After the table is created, the script inserts three rows
of data. Finally, it queries the table to retrieve all the inserted records.
These values are then used in the next step when you run the
gcloud dataproc batches submit pyspark job.
from pyspark.sql import SparkSession
spark = SparkSession.builder.appName("quickstart").getOrCreate()
# Create a namespace (dataset) if it doesn't exist
spark.sql("CREATE NAMESPACE IF NOT EXISTS `quickstart_catalog`.quickstart_namespace")
# Create the table ONLY if it doesn't already exist
spark.sql("""
CREATE OR REPLACE TABLE `quickstart_catalog`.quickstart_namespace.quickstart_table (
id INT,
name STRING
)
USING iceberg
""")
# Insert data into the table
spark.sql("""
INSERT INTO `quickstart_catalog`.quickstart_namespace.quickstart_table
VALUES (1, 'one'), (2, 'two'), (3, 'three')
""")
# Query the table and SHOW the results in the Dataproc logs
df = spark.sql("SELECT * FROM `quickstart_catalog`.quickstart_namespace.quickstart_table")
Upload the script to your Cloud Storage bucket
After you create the quickstart.py script, upload it to the Cloud Storage
bucket.
In the Google Cloud console, go to Cloud Storage buckets.
Click the name of your bucket.
On the Objects tab, click Upload > Upload files.
In the file browser, select the
quickstart.pyfile, and then click Open.
Run the Spark job
After you upload the quickstart.py script, run it as a
Managed Service for Apache Spark Spark batch job.
In Cloud Shell, run the following Managed Service for Apache Spark batch job using the
quickstart.pyscript.gcloud dataproc batches submit pyspark gs://BIGLAKE_CATALOG_ID/quickstart.py \ --project=PROJECT_ID \ --region=REGION \ --version=2.2 \ --properties="\ spark.sql.defaultCatalog=quickstart_catalog,\ spark.sql.catalog.quickstart_catalog=org.apache.iceberg.spark.SparkCatalog,\ spark.sql.catalog.quickstart_catalog.type=rest,\ spark.sql.catalog.quickstart_catalog.uri=https://biglake.googleapis.com/iceberg/v1/restcatalog,\ spark.sql.catalog.quickstart_catalog.warehouse=gs://BIGLAKE_CATALOG_ID,\ spark.sql.catalog.quickstart_catalog.io-impl=org.apache.iceberg.gcp.gcs.GCSFileIO,\ spark.sql.catalog.quickstart_catalog.header.x-goog-user-project=PROJECT_ID,\ spark.sql.catalog.quickstart_catalog.rest.auth.type=org.apache.iceberg.gcp.auth.GoogleAuthManager,\ spark.sql.extensions=org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions,\ spark.sql.catalog.quickstart_catalog.rest-metrics-reporting-enabled=false,\ spark.sql.catalog.quickstart_catalog.header.X-Iceberg-Access-Delegation=vended-credentials,\ spark.sql.catalog.quickstart_catalog.gcs.oauth2.refresh-credentials-endpoint=https://oauth2.googleapis.com/token"
Replace the following:
BIGLAKE_CATALOG_ID: the name of the Cloud Storage bucket that contains your PySpark application file.Important:
This identifier is also the name of your Catalog. For example, if you created your bucket to store your catalog and named it
iceberg-bucket, both your catalog name and bucket name areiceberg-bucket. This name is used later when you query your catalog in BigQuery, using the P.C.N.T syntax. For examplemy-project.biglake-catalog-id-name.quickstart_namespace.quickstart_table.PROJECT_ID: your Google Cloud project ID.REGION: the region to run the Managed Service for Apache Spark batch workload in.
When the job completes, it displays an output similar to the following:
Batch [cb9d84e9489d408baca4f9e7ab4c64ff] finished. metadata: '@type': type.googleapis.com/google.cloud.dataproc.v1.BatchOperationMetadata batch: projects/your-project/locations/us-central1/batches/cb9d84e9489d408baca4f9e7ab4c64ff batchUuid: 54b0b9d2-f0a1-4fdf-ae44-eead3f8e60e9 createTime: '2026-01-24T00:10:50.224097Z' description: Batch labels: goog-dataproc-batch-id: cb9d84e9489d408baca4f9e7ab4c64ff goog-dataproc-batch-uuid: 54b0b9d2-f0a1-4fdf-ae44-eead3f8e60e9 goog-dataproc-drz-resource-uuid: batch-54b0b9d2-f0a1-4fdf-ae44-eead3f8e60e9 goog-dataproc-location: us-central1 operationType: BATCH name: projects/your-project/regions/us-central1/operations/32287926-5f61-3572-b54a-fbad8940d6ef
Query the table from BigQuery
In the Google Cloud console, go to BigQuery.
In the query editor, enter the following statement. The query uses the
project.catalog.namespace.tablesyntax.SELECT * FROM `PROJECT_ID.BIGLAKE_CATALOG_ID.quickstart_namespace.quickstart_table`;Replace:
PROJECT_ID: your Google Cloud project ID.BIGLAKE_CATALOG_ID: the catalog identifier to use in BigQuery queries.Important
This identifier is also the name of your Cloud Storage bucket.
For example, if you created you bucket to store your catalog and named it
iceberg-bucket, both your catalog name and bucket name areiceberg-bucket. This is used later when you query your catalog in BigQuery, using the P.C.N.T syntax. For examplemy-project.biglake-catalog-id-name.quickstart_namespace.quickstart_table.
Click Run.
The query results show the data that you inserted with the Spark job.
Clean up
To avoid incurring charges to your Google Cloud account for the resources used on this page, follow these steps.
In the Google Cloud console, go to BigQuery.
In the query editor, run the following statement to delete the table:
DROP TABLE `PROJECT_dID.BIGLAKE_CATALOG_ID.quickstart_namespace.quickstart_table`;Go to BigLake.
Select the
quickstart_catalogcatalog, and then click Delete.Go to Cloud Storage Buckets.
Select your bucket and click Delete.
What's next
- Learn how to manage catalogs.
- Learn about BigLake tables for Apache Iceberg.