Get Database

biglake.get_database
ActionGoogle Cloudconnection required

Calls Lakehouse GET /v1/projects/{projectsId}/locations/{locationsId}/catalogs/{catalogsId}/databases/{databasesId}.

Gets the database specified by the resource name.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Lakehouse
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
location, project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Location / region (overrides connection).
stringNo———
catalog
Id of the catalog to act on, from biglake.list_catalogs — not its name.
stringYes———
database
Id of the database to act on, from biglake.list_databases — not its name.
stringYes———

Output

One shape.

result

FieldTypeExample
ok
boolean—
type
string—
hiveOptions
object—
updateTime
string—
createTime
string—
deleteTime
string—
name
string—
{
  "createTime": "",
  "deleteTime": "",
  "hiveOptions": {},
  "name": "",
  "ok": false,
  "type": "",
  "updateTime": ""
}

See Get Database run in a workflow.

In a technical demo we add the Google Lakehouse connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.