Google Dataproc Metastore API
Browse all Google APIs✓ Official Vendor SpecStorageDatabaseoauth227 EndpointsREST
For Agents
Provision and manage Dataproc Metastore services that act as a managed Hive metastore for Dataproc and BigQuery: create services, run backups, import metadata, and federate metastores.
Use for: Provision a new Dataproc Metastore service in europe-west1, Trigger a backup of an existing Dataproc Metastore service, Import Hive metadata from a Cloud Storage URI into my metastore, Create a federation that combines two metastores under one endpoint
Not supported: Does not handle Hive query execution, table data files, or cluster compute — use for metastore service lifecycle, backups, metadata imports, federations, and IAM policy only.
Dataproc Metastore is Google Cloud's managed Apache Hive metastore service that provides a centralised metadata catalog for Dataproc, BigQuery federation, and other open-source data engines. The API covers metastore service lifecycle, backups, metadata import, federations across multiple metastores, and IAM policy management on individual services. Long-running operations are returned for state-changing calls and most resources are scoped to a project location.
Install Jentic One Beta
Connect the Dataproc Metastore API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dataproc Metastore API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Dataproc Metastore API.
Provision and delete managed Hive metastore services in a Google Cloud project location
Create and list backups of metastore services for disaster recovery
Import existing Hive metadata from Cloud Storage into a metastore service
Create and manage federations that combine multiple metastores under one endpoint
Track migration executions when moving from a self-managed Hive metastore
Manage IAM policy and test IAM permissions on individual metastore services
Use Cases
Patterns agents use Dataproc Metastore API for, with concrete tasks.
★ Managed Hive metastore for Dataproc
Provision a Dataproc Metastore service so that ephemeral Dataproc clusters share a persistent Hive metadata catalog rather than each cluster maintaining its own. This lets jobs run against the same tables and partitions across cluster lifetimes and integrates cleanly with BigQuery federation queries.
Create a metastore service named lake-meta under projects/acme/locations/europe-west1 with hive metastore version 3.1.2 and tier DEVELOPER, then poll the returned operation
Metastore backup and restore
Run scheduled backups of a metastore service so that table definitions, partitions, and database metadata can be restored after an accidental drop or schema corruption. The backups resource is per-service and pairs with the import flow for restore-style workflows.
Create a backup of metastore service projects/acme/locations/europe-west1/services/lake-meta and confirm the operation completes
Metastore federation across regions
Combine multiple Dataproc Metastore services under a single federation endpoint so that data engines see one logical metastore for queries spanning regions or business units. Federations are useful for organisations that keep separate metastores per data domain but want unified access.
Create a federation named global-lake under projects/acme/locations/global with backing services from europe-west1 and us-central1
Agent integration via Jentic
AI agents managing data lake metadata can use the Dataproc Metastore API through Jentic to provision services, run scheduled backups, or import metadata from Cloud Storage URIs without holding the underlying OAuth refresh token in their prompt.
List metadataImports for service lake-meta and start a new import from gs://acme-lake/metadata/2026-06.dump if no import has run in the last 7 days
Key Endpoints
27 endpoints — dataproc metastore is google cloud's managed apache hive metastore service that provides a centralised metadata catalog for dataproc, bigquery federation, and other open-source data engines.
METHOD
PATH
DESCRIPTION
GET
/v1/{+parent}/services
List metastore services
DELETE
/v1/{+name}
Delete a metastore service or other resource
GET
/v1/{+parent}/backups
List backups for a service
GET
/v1/{+parent}/federations
List federations in a location
GET
/v1/{+parent}/metadataImports
List metadata import runs
GET
/v1/{+parent}/migrationExecutions
List migration executions
GET
/v1/{+resource}:getIamPolicy
Read IAM policy on a service
POST
/v1/{+name}:cancel
Cancel a long-running operation
GET
/v1/{+parent}/services
List metastore services
DELETE
/v1/{+name}
Delete a metastore service or other resource
GET
/v1/{+parent}/backups
List backups for a service
GET
/v1/{+parent}/federations
List federations in a location
GET
/v1/{+parent}/metadataImports
List metadata import runs
GET
/v1/{+parent}/migrationExecutions
List migration executions
GET
/v1/{+resource}:getIamPolicy
Read IAM policy on a service
POST
/v1/{+name}:cancel
Cancel a long-running operation
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google Cloud OAuth 2.0 client credentials and refresh tokens are stored encrypted in the Jentic vault. Agents receive short-lived bearer tokens scoped to cloud-platform; the refresh token and client secret never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent such as provision metastore service or import hive metadata and Jentic returns the matching operations with input schemas, so the agent does not have to read Google Cloud's discovery documents.
Time to first call
Direct integration takes 1-2 days for OAuth setup, long-running operation polling, and metadata import handling. Through Jentic the same workflows are under an hour: search, load schema, execute, poll the returned operation.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Dataproc Metastore API through Jentic.
What authentication does the Dataproc Metastore API use?
The API uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic, the OAuth credentials are held in the encrypted vault and the agent receives only a scoped bearer token; the refresh token never enters the agent's context.
Can I federate multiple metastore services through this API?
Yes, the federations endpoints under a project location let you combine multiple metastore services under a single federation endpoint, useful when teams want one logical catalog backed by per-region metastores.
What are the rate limits for the Dataproc Metastore API?
Quotas are managed per project under the Dataproc Metastore service in the Cloud Console quotas page. Long-running operations have concurrency caps in addition to per-minute request limits, so bulk lifecycle scripts should respect the operation queue.
How do I import existing Hive metadata through Jentic?
Search Jentic for import hive metadata to dataproc metastore, load the metadataImports create operation, and execute with the gs:// URI of the metadata dump and the target service name. Jentic returns the long-running operation handle for polling.
Is the Dataproc Metastore API free?
The API itself is not separately billed; you pay for the metastore service tier (DEVELOPER or ENTERPRISE) per hour and any associated storage. See the Dataproc Metastore pricing page for current rates.
Can I run Hive queries through this API?
No, this API manages metastore services themselves. To run queries, point a Dataproc cluster, BigQuery federation, or Spark job at the metastore endpoint and execute Hive or Spark SQL there.
GET STARTED