bigquery-migration client for Node.js

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

• BigQuery Migration API Node.js Client API Reference
• BigQuery Migration API Documentation
• github.com/googleapis/google-cloud-node/packages/google-cloud-bigquery-migration

Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.

Table of contents:

• Quickstart

  • Before you begin
  • Installing the client library

• Samples

• Versioning

• Contributing

• License

1. Select or create a Cloud Platform project.
2. Enable billing for your project.
3. Enable the BigQuery Migration API API.
4. Set up authentication with a service account so you can access the API from your local workstation.

npm install @google-cloud/bigquery-migration

Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.

Sample	Source Code	Try it
Migration_service.create_migration_workflow	source code
Migration_service.delete_migration_workflow	source code
Migration_service.get_migration_subtask	source code
Migration_service.get_migration_workflow	source code
Migration_service.list_migration_subtasks	source code
Migration_service.list_migration_workflows	source code
Migration_service.start_migration_workflow	source code
Migration_service.create_migration_workflow	source code
Migration_service.delete_migration_workflow	source code
Migration_service.get_migration_subtask	source code
Migration_service.get_migration_workflow	source code
Migration_service.list_migration_subtasks	source code
Migration_service.list_migration_workflows	source code
Migration_service.start_migration_workflow	source code
Sql_translation_service.translate_query	source code
Quickstart	source code

The BigQuery Migration API Node.js Client API Reference documentation also contains samples.

Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on a best-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, and can be installed through npm dist-tags. The dist-tags follow the naming convention legacy-(version). For example, npm install @google-cloud/bigquery-migration@legacy-8 installs client libraries for versions compatible with Node.js 8.

This library follows Semantic Versioning.

This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority.

More Information: Google Cloud Platform Launch Stages

Contributions welcome! See the Contributing Guide.

Please note that this README.md, the samples/README.md, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its templates in directory.

Apache Version 2.0

See LICENSE