Get desktop application:
View/edit binary Protocol Buffers messages
The Google BigQuery Data Transfer Service API enables BigQuery users to configure the transfer of their data from other Google Products into BigQuery. This service contains methods that are end user exposed. It backs up the frontend.
Returns true if valid credentials exist for the given data source and requesting user. Some data sources doesn't support service account, so we need to talk to them on behalf of the end user. This API just checks whether we have OAuth token for the particular user, which is a pre-requisite before user can create a transfer config.
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.
The data source in the form: `projects/{project_id}/dataSources/{data_source_id}`
A response indicating whether the credentials exist and are valid.
If set to `true`, the credentials exist and are valid.
Creates a new data transfer configuration.
A request to create a data transfer configuration. If new credentials are needed for this transfer configuration, an authorization code must be provided. If an authorization code is provided, the transfer configuration will be associated with the user id corresponding to the authorization code. Otherwise, the transfer configuration will be associated with the calling user.
The BigQuery project id where the transfer configuration should be created. Must be in the format /projects/{project_id}/locations/{location_id} If specified location and location of the destination bigquery dataset do not match - the request will fail.
Data transfer configuration to create.
Optional OAuth2 authorization code to use with this transfer configuration. This is required if new credentials are needed, as indicated by `CheckValidCreds`. In order to obtain authorization_code, please make a request to https://www.gstatic.com/bigquerydatatransfer/oauthz/auth?client_id=<datatransferapiclientid>&scope=<data_source_scopes>&redirect_uri=<redirect_uri> * client_id should be OAuth client_id of BigQuery DTS API for the given data source returned by ListDataSources method. * data_source_scopes are the scopes returned by ListDataSources method. * redirect_uri is an optional parameter. If not specified, then authorization code is posted to the opener of authorization flow window. Otherwise it will be sent to the redirect uri. A special value of urn:ietf:wg:oauth:2.0:oob means that authorization code should be returned in the title bar of the browser, with the page text prompting the user to copy the code and paste it in the application.
Deletes a data transfer configuration, including any associated transfer runs and logs.
A request to delete data transfer information. All associated transfer runs and log messages will be deleted as well.
The field will contain name of the resource requested, for example: `projects/{project_id}/transferConfigs/{config_id}`
Deletes the specified transfer run.
A request to delete data transfer run information.
The field will contain name of the resource requested, for example: `projects/{project_id}/transferConfigs/{config_id}/runs/{run_id}`
Retrieves a supported data source and returns its settings, which can be used for UI rendering.
A request to get data source info.
The field will contain name of the resource requested, for example: `projects/{project_id}/dataSources/{data_source_id}`
Returns information about a data transfer config.
A request to get data transfer information.
The field will contain name of the resource requested, for example: `projects/{project_id}/transferConfigs/{config_id}`
Returns information about the particular transfer run.
A request to get data transfer run information.
The field will contain name of the resource requested, for example: `projects/{project_id}/transferConfigs/{config_id}/runs/{run_id}`
Lists supported data sources and returns their settings, which can be used for UI rendering.
Request to list supported data sources and their data transfer settings.
The BigQuery project id for which data sources should be returned. Must be in the form: `projects/{project_id}`
Pagination token, which can be used to request a specific page of `ListDataSourcesRequest` list results. For multiple-page results, `ListDataSourcesResponse` outputs a `next_page` token, which can be used as the `page_token` value to request the next page of list results.
Page size. The default page size is the maximum value of 1000 results.
Returns list of supported data sources and their metadata.
List of supported data sources and their transfer settings.
Output only. The next-pagination token. For multiple-page list results, this token can be used as the `ListDataSourcesRequest.page_token` to request the next page of list results.
Returns information about all data transfers in the project.
A request to list data transfers configured for a BigQuery project.
The BigQuery project id for which data sources should be returned: `projects/{project_id}`.
When specified, only configurations of requested data sources are returned.
Pagination token, which can be used to request a specific page of `ListTransfersRequest` list results. For multiple-page results, `ListTransfersResponse` outputs a `next_page` token, which can be used as the `page_token` value to request the next page of list results.
Page size. The default page size is the maximum value of 1000 results.
The returned list of pipelines in the project.
Output only. The stored pipeline transfer configurations.
Output only. The next-pagination token. For multiple-page list results, this token can be used as the `ListTransferConfigsRequest.page_token` to request the next page of list results.
Returns user facing log messages for the data transfer run.
A request to get user facing log messages associated with data transfer run.
Transfer run name in the form: `projects/{project_id}/transferConfigs/{config_Id}/runs/{run_id}`.
Pagination token, which can be used to request a specific page of `ListTransferLogsRequest` list results. For multiple-page results, `ListTransferLogsResponse` outputs a `next_page` token, which can be used as the `page_token` value to request the next page of list results.
Page size. The default page size is the maximum value of 1000 results.
Message types to return. If not populated - INFO, WARNING and ERROR messages are returned.
The returned list transfer run messages.
Output only. The stored pipeline transfer messages.
Output only. The next-pagination token. For multiple-page list results, this token can be used as the `GetTransferRunLogRequest.page_token` to request the next page of list results.
Returns information about running and completed jobs.
A request to list data transfer runs. UI can use this method to show/filter specific data transfer runs. The data source can use this method to request all scheduled transfer runs.
Name of transfer configuration for which transfer runs should be retrieved. Format of transfer configuration resource name is: `projects/{project_id}/transferConfigs/{config_id}`.
When specified, only transfer runs with requested states are returned.
Pagination token, which can be used to request a specific page of `ListTransferRunsRequest` list results. For multiple-page results, `ListTransferRunsResponse` outputs a `next_page` token, which can be used as the `page_token` value to request the next page of list results.
Page size. The default page size is the maximum value of 1000 results.
Indicates how run attempts are to be pulled.
The returned list of pipelines in the project.
Output only. The stored pipeline transfer runs.
Output only. The next-pagination token. For multiple-page list results, this token can be used as the `ListTransferRunsRequest.page_token` to request the next page of list results.
Creates transfer runs for a time range [start_time, end_time]. For each date - or whatever granularity the data source supports - in the range, one transfer run is created. Note that runs are created per UTC time in the time range.
A request to schedule transfer runs for a time range.
Transfer configuration name in the form: `projects/{project_id}/transferConfigs/{config_id}`.
Start time of the range of transfer runs. For example, `"2017-05-25T00:00:00+00:00"`.
End time of the range of transfer runs. For example, `"2017-05-30T00:00:00+00:00"`.
A response to schedule transfer runs for a time range.
The transfer runs that were scheduled.
Updates a data transfer configuration. All fields must be set, even if they are not updated.
A request to update a transfer configuration. To update the user id of the transfer configuration, an authorization code needs to be provided.
Data transfer configuration to create.
Optional OAuth2 authorization code to use with this transfer configuration. If it is provided, the transfer configuration will be associated with the authorizing user. In order to obtain authorization_code, please make a request to https://www.gstatic.com/bigquerydatatransfer/oauthz/auth?client_id=<datatransferapiclientid>&scope=<data_source_scopes>&redirect_uri=<redirect_uri> * client_id should be OAuth client_id of BigQuery DTS API for the given data source returned by ListDataSources method. * data_source_scopes are the scopes returned by ListDataSources method. * redirect_uri is an optional parameter. If not specified, then authorization code is posted to the opener of authorization flow window. Otherwise it will be sent to the redirect uri. A special value of urn:ietf:wg:oauth:2.0:oob means that authorization code should be returned in the title bar of the browser, with the page text prompting the user to copy the code and paste it in the application.
Required list of fields to be updated in this request.
Represents data source metadata. Metadata is sufficient to render UI and request proper OAuth tokens.
Used as response type in: DataTransferService.GetDataSource
Used as field type in:
Output only. Data source resource name.
Data source id.
User friendly data source name.
User friendly data source description string.
Data source client id which should be used to receive refresh token. When not supplied, no offline credentials are populated for data transfer.
Api auth scopes for which refresh token needs to be obtained. Only valid when `client_id` is specified. Ignored otherwise. These are scopes needed by a data source to prepare data and ingest them into BigQuery, e.g., https://www.googleapis.com/auth/bigquery
Deprecated. This field has no effect.
Indicates whether the data source supports multiple transfers to different BigQuery targets.
The number of seconds to wait for an update from the data source before BigQuery marks the transfer as failed.
Default data transfer schedule. Examples of valid schedules include: `1st,3rd monday of month 15:30`, `every wed,fri of jan,jun 13:15`, and `first sunday of quarter 00:00`.
Specifies whether the data source supports a user defined schedule, or operates on the default schedule. When set to `true`, user can override default schedule.
Data source parameters.
Url for the help document for this data source.
Indicates the type of authorization.
Specifies whether the data source supports automatic data refresh for the past few days, and how it's supported. For some data sources, data might not be complete until a few days later, so it's useful to refresh data automatically.
Default data refresh window on days. Only meaningful when `data_refresh_type` = `SLIDING_WINDOW`.
Disables backfilling and manual run scheduling for the data source.
The minimum interval for scheduler to schedule runs.
The type of authorization needed for this data source.
Used in:
Type unspecified.
Use OAuth 2 authorization codes that can be exchanged for a refresh token on the backend.
Return an authorization code for a given Google+ page that can then be exchanged for a refresh token on the backend.
Represents how the data source supports data auto refresh.
Used in:
The data source won't support data auto refresh, which is default value.
The data source supports data auto refresh, and runs will be scheduled for the past few days. Does not allow custom values to be set for each transfer config.
The data source supports data auto refresh, and runs will be scheduled for the past few days. Allows custom values to be set for each transfer config.
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.
Used in:
Parameter identifier.
Parameter display name in the user interface.
Parameter description.
Parameter type.
Is parameter required.
Can parameter have multiple values.
Regular expression which can be used for parameter validation.
All possible values for the parameter.
For integer and double values specifies minimum allowed value.
For integer and double values specifies maxminum allowed value.
When parameter is a record, describes child fields.
Description of the requirements for this field, in case the user input does not fulfill the regex pattern or min/max values.
URL to a help document to further explain the naming requirements.
Cannot be changed after initial creation.
If set to true, schema should be taken from the parent with the same parameter_id. Only applicable when parameter type is RECORD.
Parameter type.
Used in:
Type unspecified.
String parameter.
Integer parameter (64-bits). Will be serialized to json as string.
Double precision floating point parameter.
Boolean parameter.
Record parameter.
Page ID for a Google+ Page.
Represents which runs should be pulled.
Used in:
All runs should be returned.
Only latest run per day should be returned.
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.
Used as response type in: DataTransferService.CreateTransferConfig, DataTransferService.GetTransferConfig, DataTransferService.UpdateTransferConfig
Used as field type in: , ,
The resource name of the transfer config. Transfer config names have the form `projects/{project_id}/transferConfigs/{config_id}`. Where `config_id` is usually a uuid, even though it is not guaranteed or required. The name is ignored when creating a transfer config.
The BigQuery target dataset id.
User specified display name for the data transfer.
Data source id. Cannot be changed once data transfer is created.
Data transfer specific parameters.
Data transfer schedule. If the data source does not support a custom schedule, this should be empty. If it is empty, the default value for the data source will be used. The specified times are in UTC. Examples of valid format: `1st,3rd monday of month 15:30`, `every wed,fri of jan,jun 13:15`, and `first sunday of quarter 00:00`. See more explanation about the format here: https://cloud.google.com/appengine/docs/flexible/python/scheduling-jobs-with-cron-yaml#the_schedule_format NOTE: the granularity should be at least 8 hours, or less frequent.
The number of days to look back to automatically refresh the data. For example, if `data_refresh_window_days = 10`, then every day BigQuery reingests data for [today-10, today-1], rather than ingesting data for just [today-1]. Only valid if the data source supports the feature. Set the value to 0 to use the default value.
Is this config disabled. When set to true, no runs are scheduled for a given transfer.
Output only. Data transfer modification time. Ignored by server on input.
Output only. Next time when data transfer will run.
Output only. State of the most recently updated transfer run.
Output only. Unique ID of the user on whose behalf transfer is done. Applicable only to data sources that do not support service accounts. When set to 0, the data source service account credentials are used. May be negative. Note, that this identifier is not stable. It may change over time even for the same user.
Output only. Region in which BigQuery dataset is located.
Represents a user facing message for a particular data transfer run.
Used in:
Time when message was logged.
Message severity.
Message text.
Represents data transfer user facing message severity.
Used in: ,
No severity specified.
Informational message.
Warning message.
Error message.
Represents a data transfer run.
Used as response type in: DataTransferService.GetTransferRun
Used as field type in: ,
The resource name of the transfer run. Transfer run names have the form `projects/{project_id}/locations/{location}/transferConfigs/{config_id}/runs/{run_id}`. The name is ignored when creating a transfer run.
Minimum time after which a transfer run can be started.
For batch transfer runs, specifies the date and time that data should be ingested.
Status of the transfer run.
Output only. Time when transfer run was started. Parameter ignored by server for input requests.
Output only. Time when transfer run ended. Parameter ignored by server for input requests.
Output only. Last time the data transfer run state was updated.
Output only. Data transfer specific parameters.
Output only. The BigQuery target dataset id.
Output only. Data source id.
Data transfer run state. Ignored for input requests.
Output only. Unique ID of the user on whose behalf transfer is done. Applicable only to data sources that do not support service accounts. When set to 0, the data source service account credentials are used. May be negative. Note, that this identifier is not stable. It may change over time even for the same user.
Output only. Describes the schedule of this transfer run if it was created as part of a regular schedule. For batch transfer runs that are scheduled manually, this is empty. NOTE: the system might choose to delay the schedule depending on the current load, so `schedule_time` doesn't always matches this.
Represents data transfer run state.
Used in: , ,
State placeholder.
Data transfer is scheduled and is waiting to be picked up by data transfer backend.
Data transfer is in progress.
Data transfer completed successsfully.
Data transfer failed.
Data transfer is cancelled.
DEPRECATED. Represents data transfer type.
Used in:
Invalid or Unknown transfer type placeholder.
Batch data transfer.
Streaming data transfer. Streaming data source currently doesn't support multiple transfer configs per project.