API Reference google_api_big_query_data_transfer v0.23.0

Modules

API client metadata for GoogleApi.BigQueryDataTransfer.V1.

API calls for all endpoints tagged Projects.

Handle Tesla connections for GoogleApi.BigQueryDataTransfer.V1.

A request to determine whether the user has valid credentials. This method is used to limit the number of OAuth popups in the user interface. The user id is inferred from the API call context. If the data source has the Google+ authorization type, this method returns false, as it cannot be determined whether the credentials are already valid merely based on the user id.

A response indicating whether the credentials exist and are valid.

Represents data source metadata. Metadata is sufficient to render UI and request proper OAuth tokens.

Represents a data source parameter with validation rules, so that parameters can be rendered in the UI. These parameters are given to us by supported data sources, and include all needed information for rendering and validation. Thus, whoever uses this api can decide to generate either generic ui, or custom data source specific forms.

Represents preferences for sending email notifications for transfer run events.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for Empty is empty JSON object {}.

Returns list of supported data sources and their metadata.

The response message for Locations.ListLocations.

The returned list of pipelines in the project.

The returned list transfer run messages.

The returned list of pipelines in the project.

A resource that represents Google Cloud Platform location.

Options customizing the data transfer schedule.

A request to schedule transfer runs for a time range.

A response to schedule transfer runs for a time range.

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

A specification for a time range, this will request transfer runs with run_time between start_time (inclusive) and end_time (exclusive).

Represents a data transfer configuration. A transfer configuration contains all metadata needed to perform a data transfer. For example, destination_dataset_id specifies where data should be stored. When a new transfer configuration is created, the specified destination_dataset_id is created when needed and shared with the appropriate data source service account.

Represents a user facing message for a particular data transfer run.

Represents a data transfer run.