Delete a catalog

When you delete a catalog (such as an Apache Iceberg REST catalog or Apache Hive catalog), the system unregisters the metadata management endpoint from the Lakehouse runtime catalog.

Although this removes the catalog from Lakehouse for Apache Iceberg, it does not automatically delete the underlying Cloud Storage bucket or your stored data files.

Before you begin

1. Read About the Lakehouse runtime catalog to understand how the Lakehouse runtime catalog works and the limitations for the service.
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 the resourcemanager.projects.create permission. Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to project selector

Verify that billing is enabled for your Google Cloud project.

Enable the BigLake API.

Roles required to enable APIs

To enable APIs, you need the Service Usage Admin IAM role (roles/serviceusage.serviceUsageAdmin), which contains the serviceusage.services.enable permission. Learn how to grant roles.

Enable the API

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 the resourcemanager.projects.create permission. Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to project selector

Verify that billing is enabled for your Google Cloud project.

Enable the BigLake API.

Roles required to enable APIs

To enable APIs, you need the Service Usage Admin IAM role (roles/serviceusage.serviceUsageAdmin), which contains the serviceusage.services.enable permission. Learn how to grant roles.

Enable the API

Required roles

To get the permissions that you need to delete a catalog, ask your administrator to grant you the following IAM roles on your project:

• All:
  • BigLake Admin (roles/biglake.admin)
  • Storage Admin (roles/storage.admin)

For more information about granting roles, see Manage access to projects, folders, and organizations.

You might also be able to get the required permissions through custom roles or other predefined roles.

Delete a catalog

Delete a catalog endpoint.

Console

Note: BigLake catalogs are not supported in the Google Cloud console. To delete a BigLake catalog, use gcloud or the REST API.

1. In the Google Cloud console, open the Lakehouse page.

   Go to Lakehouse

2. In the row of the catalog that you're deleting, click More catalog actions > Delete.

3. In the delete dialog, enter DELETE and click Delete.

gcloud

To delete a catalog using gcloud, run the gcloud biglake iceberg catalogs delete command.

gcloud biglake iceberg catalogs delete CATALOG_ID \
    --project="PROJECT_ID"

Replace the following:

• CATALOG_ID: the ID of your catalog.
• PROJECT_ID: your Google Cloud project ID.

REST

To delete a catalog management endpoint using the REST API, make a DELETE request to the DeleteIcebergCatalog endpoint:

DELETE /iceberg/v1/restcatalog/extensions/projects/PROJECT_ID/catalogs/CATALOG_ID

Note: You cannot delete a catalog that still contains namespaces or tables.

Replace the following:

• PROJECT_ID: your Google Cloud project ID.
• CATALOG_ID: the ID of your catalog.