Statement families
Discover objects
The following script selects the configured example catalog and namespace before discovery. The last statement supplies the displayed result. Run a statement separately to inspect its own output.Catalogs and namespaces
A catalog registers a metadata provider and its connection options. A namespace groups tables and views within that catalog. USE changes the current session context; it does not move data.
DATABASE and SCHEMA have supported namespace spellings. Register Hub’s Lakekeeper connection and its MinIO access in Catalogs, then select that catalog in your SQL client. See Hub setup.
Definitions and changes
CREATE TABLE accepts an explicit schema or AS SELECT. USING, OPTIONS, PARTITIONED BY, LOCATION, COMMENT, and TBLPROPERTIES describe the provider, layout, and metadata. IF NOT EXISTS avoids a name collision; it does not check that an existing table matches the requested definition. ALTER TABLE supports specific schema and property changes; it is not a promise that every Spark schema-evolution command is available. DROP removes an object according to its catalog semantics. Examples that create and remove objects are confined to the write lab.Secrets and credentials
Named secrets and credentials have CREATE, ALTER, DROP, SHOW, and DESCRIBE SQL forms. A secret can hold a literal or an external reference; a credential identifies a provider and named options or secrets. Sensitive SQL is hidden in history and audit output. Use the product’s Access pages to create and inspect these resources without putting secret values in shared examples.
See secret SQL and HTTP examples, credential SQL and HTTP examples, and catalog SQL and HTTP examples. There are no dedicated Unified secrets or credentials REST routes. SHOW and DESCRIBE for access resources return metadata and references, rather than secret values.