Schema and Edit Schema

A schema is a row description. It defines the number of fields
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

Click Edit
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this
  option to view the schema only.

• Change to built-in property:
  choose this option to change the schema to Built-in for local changes.

• Update repository connection:
  choose this option to change the schema stored in the repository and decide whether
  to propagate the changes to all the Jobs upon completion. If you just want to
  propagate the changes to the current Job, you can select No upon completion and choose this schema metadata
  again in the Repository Content
  window.

Built-In: You create and store the schema locally for this component
only.

Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

• OAuth 2.0: authenticate the access using
  OAuth credentials. When selecting this mode, the parameters to be
  defined in the Basic settings view are
  Client ID, Client
  secret and Authorization
  code.
• Service account: authenticate using a Google
  account that is associated with your Google Cloud Platform project.
  When selecting this mode, the parameter to be defined in the
  Basic settings view is Service
  account credentials file.

For further information about how to create a Google service
account and obtain the credentials file, see Getting Started with
Authentication from the Google documentation.

Client ID and Client
secret

Paste the client ID and the client secret, both created and viewable on the
API Access tab view of the project hosting the Google BigQuery service and the Cloud
Storage service you need to use.

To enter the client secret, click the […] button next
to the client secret field, and then in the pop-up dialog box enter the client secret
between double quotes and click OK to save the
settings.

Project ID

Paste the ID of the project hosting the Google BigQuery service you
need to use.

The ID of your project can be found in the URL of the Google
API Console, or by hovering your mouse pointer over the name of the
project in the BigQuery Browser Tool.

Authorization code

Paste the authorization code provided by Google for the access you are
building.

To obtain the authorization code, you need to execute the Job using this
component and when this Job pauses execution to print out an URL address, you
navigate to this address to copy the authorization code displayed.

Use legacy SQL and Query

If the query to be used is the
legacy SQL of BigQuery, select this Use legacy
SQL check box. For further information about this legacy
SQL, see Legacy SQL query reference
from the Google BigQuery documentation.

token properties File Name

Enter the path to, or browse to the refresh token file you need to use.

At the first Job execution using the Authorization
code you have obtained from Google BigQuery, the value in this field
is the directory and the name of that refresh token file to be created and used; if
that token file has been created and you need to reuse it, you have to specify its
directory and file name in this field.

With only the token file name entered,
Talend Studio
considers the directory of that token file to be the root of the Studio
folder.

For further information about the refresh token, see the manual of Google
BigQuery.

Advanced Separator (for number)

Select this check box to change the separator used for the
numbers.

Encoding

Select the encoding from the list or select Custom
and define it manually. This field is compulsory for database data handling. The
supported encodings depend on the JVM that you are using. For more information, see
https://docs.oracle.com.

Result size

Select the option depending on the volume of the query result.

By default, the Small option is used, but when the
query result is larger than the maximum response size, you
need to select the Large option.

If the volume of the result is not certain, select
Auto.

tStatCatcher Statistics

Select this check box to collect the log data at the component
level.

Global Variables

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.

Usage rule

It can be a starting or an end component. When starting
a Job, it sends the extracted data to the component that follows it;
When ending a Job, it deletes a given table.

This component automatically detects and
supports both multi-regional locations and regional locations. When using the
regional locations, the buckets and the datasets to be used must be in the same
locations.