Dataproc Metastore: Node.js Client

Metastore client for Node.js

A comprehensive list of changes in each version may be found inthe CHANGELOG.

• Dataproc Metastore Node.js Client API Reference
• Dataproc Metastore Documentation
• github.com/googleapis/google-cloud-node/packages/google-cloud-metastore

Read more about the client libraries for Cloud APIs, including the olderGoogle APIs Client Libraries, inClient Libraries Explained.

Table of contents:

• Quickstart
  • Before you begin
  • Installing the client library
  • Using the client library
• Samples
• Versioning
• Contributing
• License

Quickstart

Before you begin

1. Select or create a Cloud Platform project.
2. Enable billing for your project.
3. Enable the Dataproc Metastore API.
4. Set up authentication so you can access theAPI from your local workstation.

Installing the client library

npm install @google-cloud/dataproc-metastore

Using the client library

// Imports the Google Cloud client libraryconst {DataprocMetastoreClient} = require('@google-cloud/dataproc-metastore');// TODO(developer): replace with your prefered project ID.// const projectId = 'my-project'// const location = 'my-location'// Creates a clientconst client = newDataprocMetastoreClient();async function listServices() {  const [services] = await client.listServices({    parent: `projects/${projectId}/locations/${location}`,  });  console.info(services);}listServices();

Samples

Samples are in thesamples/ directory. Each sample'sREADME.md has instructions for running its sample.

Sample	Source Code	Try it
Dataproc_metastore.alter_metadata_resource_location	source code
Dataproc_metastore.create_backup	source code
Dataproc_metastore.create_metadata_import	source code
Dataproc_metastore.create_service	source code
Dataproc_metastore.delete_backup	source code
Dataproc_metastore.delete_service	source code
Dataproc_metastore.export_metadata	source code
Dataproc_metastore.get_backup	source code
Dataproc_metastore.get_metadata_import	source code
Dataproc_metastore.get_service	source code
Dataproc_metastore.list_backups	source code
Dataproc_metastore.list_metadata_imports	source code
Dataproc_metastore.list_services	source code
Dataproc_metastore.move_table_to_database	source code
Dataproc_metastore.query_metadata	source code
Dataproc_metastore.restore_service	source code
Dataproc_metastore.update_metadata_import	source code
Dataproc_metastore.update_service	source code
Dataproc_metastore_federation.create_federation	source code
Dataproc_metastore_federation.delete_federation	source code
Dataproc_metastore_federation.get_federation	source code
Dataproc_metastore_federation.list_federations	source code
Dataproc_metastore_federation.update_federation	source code
Dataproc_metastore.alter_metadata_resource_location	source code
Dataproc_metastore.create_backup	source code
Dataproc_metastore.create_metadata_import	source code
Dataproc_metastore.create_service	source code
Dataproc_metastore.delete_backup	source code
Dataproc_metastore.delete_service	source code
Dataproc_metastore.export_metadata	source code
Dataproc_metastore.get_backup	source code
Dataproc_metastore.get_metadata_import	source code
Dataproc_metastore.get_service	source code
Dataproc_metastore.list_backups	source code
Dataproc_metastore.list_metadata_imports	source code
Dataproc_metastore.list_services	source code
Dataproc_metastore.move_table_to_database	source code
Dataproc_metastore.query_metadata	source code
Dataproc_metastore.remove_iam_policy	source code
Dataproc_metastore.restore_service	source code
Dataproc_metastore.update_metadata_import	source code
Dataproc_metastore.update_service	source code
Dataproc_metastore_federation.create_federation	source code
Dataproc_metastore_federation.delete_federation	source code
Dataproc_metastore_federation.get_federation	source code
Dataproc_metastore_federation.list_federations	source code
Dataproc_metastore_federation.update_federation	source code
Dataproc_metastore.alter_metadata_resource_location	source code
Dataproc_metastore.create_backup	source code
Dataproc_metastore.create_metadata_import	source code
Dataproc_metastore.create_service	source code
Dataproc_metastore.delete_backup	source code
Dataproc_metastore.delete_service	source code
Dataproc_metastore.export_metadata	source code
Dataproc_metastore.get_backup	source code
Dataproc_metastore.get_metadata_import	source code
Dataproc_metastore.get_service	source code
Dataproc_metastore.list_backups	source code
Dataproc_metastore.list_metadata_imports	source code
Dataproc_metastore.list_services	source code
Dataproc_metastore.move_table_to_database	source code
Dataproc_metastore.query_metadata	source code
Dataproc_metastore.remove_iam_policy	source code
Dataproc_metastore.restore_service	source code
Dataproc_metastore.update_metadata_import	source code
Dataproc_metastore.update_service	source code
Dataproc_metastore_federation.create_federation	source code
Dataproc_metastore_federation.delete_federation	source code
Dataproc_metastore_federation.get_federation	source code
Dataproc_metastore_federation.list_federations	source code
Dataproc_metastore_federation.update_federation	source code
Quickstart	source code

TheDataproc Metastore Node.js Client API Reference documentationalso contains samples.

Supported Node.js Versions

Our client libraries follow theNode.js release schedule.Libraries are compatible with all currentactive andmaintenance versions ofNode.js.If you are using an end-of-life version of Node.js, we recommend that you updateas soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on abest-efforts basis with the following warnings:

• Legacy versions are not tested in continuous integration.
• Some security patches and features cannot be backported.
• Dependencies cannot be kept up-to-date.

Client libraries targeting some end-of-life versions of Node.js are available, andcan be installed through npmdist-tags.The dist-tags follow the naming conventionlegacy-(version).For example,npm install @google-cloud/dataproc-metastore@legacy-8 installs client librariesfor versions compatible with Node.js 8.

Versioning

This library followsSemantic Versioning.

This library is considered to bestable. The code surface will not change in backwards-incompatible waysunless absolutely necessary (e.g. because of critical security issues) or withan extensive deprecation period. Issues and requests againststable librariesare addressed with the highest priority.

More Information:Google Cloud Platform Launch Stages

Contributing

Contributions welcome! See theContributing Guide.

Please note that thisREADME.md, thesamples/README.md,and a variety of configuration files in this repository (including.nycrc andtsconfig.json)are generated from a central template. To edit one of these files, make an editto its templates indirectory.

License

Apache Version 2.0

SeeLICENSE