Can HumDay connect to Google Dataproc Metastore?

Yes. HumDay reads Google Dataproc Metastore's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 23 operations are documented.

Do I need to write code to automate Google Dataproc Metastore?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Dataproc Metastore account.

What can HumDay do in Google Dataproc Metastore?

15 of the 23 documented operations change something in Google Dataproc Metastore, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Dataproc Metastore account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Dataproc Metastore is held behind that approval.

Automate Google Dataproc Metastore

HumDay reads Google Dataproc Metastore’s own published API description and derives 23 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Dataproc Metastore is

The Dataproc Metastore API is used to manage the lifecycle and configuration of metastore services.

API host: metastore.googleapis.com

What HumDay can do in Google Dataproc Metastore

15 documented operations change something in Google Dataproc Metastore.

POSTCreates a new backup in a given project and location./v1beta/{parent}/backups
POSTCreates a new MetadataImport in a given project and location./v1beta/{parent}/metadataImports
POSTQuery DPMS metadata./v1beta/{service}:queryMetadata
POSTCreates a metastore service in a project and location./v1beta/{parent}/services
POSTCreates a metastore federation in a project and location./v1beta/{parent}/federations
DELETEDeletes a single backup./v1beta/{name}
PATCHUpdates a single import./v1beta/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1beta/{name}:cancel
POSTRestores a service from a backup./v1beta/{service}:restore
POSTSets the access control policy on the specified resource./v1beta/{resource}:setIamPolicy
POSTAlter metadata resource location./v1beta/{service}:alterLocation
POSTExports metadata from a service./v1beta/{service}:exportMetadata
POSTReturns permissions that a caller has on the specified resource./v1beta/{resource}:testIamPermissions
POSTMove a table to another database./v1beta/{service}:moveTableToDatabase
POSTRemoves the attached IAM policies for a resource/v1beta/{resource}:removeIamPolicy

What HumDay can read from Google Dataproc Metastore

These are the operations a schedule or a trigger can watch.

GETGets details of a single import./v1beta/{name}
GETGets the access control policy for a resource./v1beta/{resource}:getIamPolicy
GETLists information about the supported locations for this service./v1beta/{name}/locations
GETLists backups in a service./v1beta/{parent}/backups
GETLists operations that match the specified filter in the request./v1beta/{name}/operations
GETLists services in a project and location./v1beta/{parent}/services
GETLists federations in a project and location./v1beta/{parent}/federations
GETLists imports in a service./v1beta/{parent}/metadataImports

How automating Google Dataproc Metastore works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Dataproc Metastore account.
Grant access, then go live. You approve the specific Google Dataproc Metastore operations it may use — and only those.