Google Dataproc Metastore
The Dataproc Metastore API is used to manage the lifecycle and configuration of metastore services (Google OAuth2).
OCNORA ships 11 typed Google Dataproc Metastore operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Dataproc Metastore
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Dataproc Metastore
Operations, grouped by what they do to your data.
Create and send 2
Read and search 4
Update 2
Delete and cancel 2
Other operations 1
A sample Google Dataproc Metastore workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Dataproc Metastore trigger is needed.
- 2Get Federationdataproc_metastore.get_federationGets the details of a single federation.
- 3Alter Locationdataproc_metastore.alter_locationAlter metadata resource location. The metadata resource can be a database, table, or partition.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 11
- Alter LocationAlter metadata resource location. The metadata resource can be a database, table, or partition.dataproc_metastore.alter_location
- Create FederationCreates a metastore federation in a project and location.dataproc_metastore.create_federation
- Create ServiceCreates a metastore service in a project and location.dataproc_metastore.create_service
- Delete FederationDeletes a single federation.dataproc_metastore.delete_federation
- Delete ServiceDeletes a single service.dataproc_metastore.delete_service
- Get FederationGets the details of a single federation.dataproc_metastore.get_federation
- Get ServiceGets the details of a single service.dataproc_metastore.get_service
- List FederationsLists federations in a project and location.dataproc_metastore.list_federations
- List ServicesLists services in a project and location.dataproc_metastore.list_services
- Update FederationUpdates the fields of a federation.dataproc_metastore.update_federation
- Update ServiceUpdates the parameters of a single service.dataproc_metastore.update_service
Google Dataproc Metastore questions
- How does OCNORA authenticate with Google Dataproc Metastore?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Dataproc Metastore?
- 11 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Dataproc Metastore operation I need is not listed?
- Where Google Dataproc Metastore has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Dataproc Metastore?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Dataproc Metastore calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Dataproc Metastore workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.