Drops per-table graph configuration entries from the session registry and catalog, removing the column mappings that define how tables participate in graph definitions.
DROP GRAPH CONFIG [<table>]## Overview DROP GRAPH CONFIG removes per-table graph configuration entries that control how individual tables are interpreted within graph definitions. These entries are created automatically by CREATE GRAPH (one entry for the vertex table and one for the edge table). They store the column mappings (ID column, source/target columns, weight column, property mode, etc.) that the engine uses when building the CSR topology. This command operates at the table level, not the graph definition level. It is a lower-level operation than DROP GRAPH. Use DROP GRAPH to remove a complete named graph definition; use DROP GRAPH CONFIG when you need fine-grained control over individual table configurations. ## Behavior ### With a Table Name When a fully qualified table name is provided: 1. The engine removes the graph configuration for that specific table from the session graph config registry. 2. If the table name is a three-part reference (zone.schema.table), the engine also sends a delete request to the catalog database to remove the persisted graph table mapping (best-effort). 3. Any graph definition that references this table will lose its column mapping. Subsequent Cypher queries against that graph will fail unless the configuration is re-created via CREATE GRAPH. ### Without a Table Name When no table name is provided: 1. The engine clears all graph configurations from the session graph config registry. 2. All graph definitions that depend on these configurations lose their column mappings. 3. The catalog database is not modified (only session state is cleared). ## Relationship to DROP GRAPH DROP GRAPH and DROP GRAPH CONFIG serve different purposes: - **DROP GRAPH** removes a named graph definition (the logical graph entity) and its associated per-table configs. - **DROP GRAPH CONFIG** removes only the per-table column mappings without touching the named graph definition. In most workflows, DROP GRAPH is the preferred command. DROP GRAPH CONFIG is useful in advanced scenarios such as debugging misconfigured column mappings, resetting session state, or migrating a table from one graph definition to another. ## Access Control | Privilege | Object | Notes | |-----------|--------|-------| | Owner or ADMIN | Table | Required when dropping config for a specific table. | ## Compatibility DROP GRAPH CONFIG is a DeltaForge extension. It has no equivalent in SQL/PGQ or openCypher specifications.
| Name | Type | Description |
|---|---|---|
table | Specifies the fully qualified table name (zone.schema.table) whose graph configuration should be removed. When omitted, all graph configurations in the session registry are cleared. |
-- Drop graph configuration for a specific edge table
DROP GRAPH CONFIG gold.social.friendships;-- Drop graph configuration for a specific vertex table
DROP GRAPH CONFIG gold.social.persons;-- Drop all graph configurations in the session
DROP GRAPH CONFIG;-- Reset and reconfigure: drop old config, then create a new graph
DROP GRAPH CONFIG gold.network.edges;
DROP GRAPH IF EXISTS network_graph;
CREATE GRAPH network_graph
VERTEX TABLE gold.network.nodes ID COLUMN node_id
EDGE TABLE gold.network.edges SOURCE COLUMN from_node TARGET COLUMN to_node
DIRECTED;