Get Service
dataproc_metastore.get_service
ActionGoogle Cloudconnection required
Calls Dataproc Metastore GET /v1/projects/{projectsId}/locations/{locationsId}/services/{servicesId}.
Gets the details of a single service.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Dataproc Metastore
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- location, project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Location / region (overrides connection). | string | No | — | — | — |
service Id of the service to act on, from dataproc_metastore.list_services — not its name. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
state | string | — |
tier | string | — |
uid | string | — |
stateMessage | string | — |
metadataIntegration | object | — |
databaseType | string | — |
{
"databaseType": "",
"metadataIntegration": {},
"ok": false,
"state": "",
"stateMessage": "",
"tier": "",
"uid": ""
}Related Google Dataproc Metastore nodes
See Get Service run in a workflow.
In a technical demo we add the Google Dataproc Metastore connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.