Delete a namespace

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

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

If a namespace does not contain any tables, you can delete it.

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 namespace, 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 namespace

1. In the Google Cloud console, go to the Lakehouse page.

   Go to Lakehouse

2. Select the catalog that contains the namespace to delete.

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

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