Delete a catalog

When you delete an Apache Iceberg REST catalog from the Google Cloud console, 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 warehouse bucket or your stored data files.

Before you begin

1. Verify that billing is enabled for your Google Cloud project.

2. 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 in the Google Cloud console, ask your administrator to grant you the following IAM roles on your project:

• 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

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.