DROP CATALOG INTEGRATION

The DROP CATALOG INTEGRATION command removes a previously created catalog integration from the system.

Syntax

DROP CATALOG INTEGRATION [IF EXISTS] integration_name;

• IF EXISTS: (Optional) Prevents an error if the specified integration does not exist.
• integration_name: The name of the catalog integration to drop.

Examples

-- Drop a catalog integration
DROP CATALOG INTEGRATION glue_catalog_int;

-- Drop a catalog integration if it exists
DROP CATALOG INTEGRATION IF EXISTS rest_catalog_int;

Behavior

When you drop a catalog integration:

1. The integration is removed from the system catalog.
2. Any active sessions using the catalog integration will be affected and may encounter errors.
3. The actual external catalog and its metadata are not affected; only the integration definition is removed.

Error Handling

If you attempt to drop a catalog integration that does not exist and you do not include the IF EXISTS clause, an error will be returned:

Error: Catalog integration 'non_existent' does not exist.

Including the IF EXISTS clause prevents this error and makes the command a no-op if the integration does not exist.

Related Commands

• CREATE CATALOG INTEGRATION: Creates a new catalog integration.
• USE CATALOG: Sets the current catalog to use for queries.

Information Schema

You can view information about existing catalog integrations using the information_schema.catalog_integrations view:

SELECT * FROM information_schema.catalog_integrations;