# tBigQueryOutputBulk Creates a .txt or .csv file for the data of large size so that you can process it according to your needs before transferring it to Google BigQuery. The tBigQueryOutputBulk and tBigQueryBulkExec components are generally used together as parts of a two step process. In the first step, an output file is generated. In the second step, this file is used to feed a dataset. These two steps are fused together in the tBigQueryOutput component, detailed in a separate section. The advantage of using two separate components is that the data can be transformed before it is loaded in the dataset. This component writes given data into a .txt or .csv file, ready to be transferred to Google BigQuery. ## tBigQueryOutputBulk Standard properties These properties are used to configure tBigQueryOutputBulk running in the Standard Job framework. The Standard tBigQueryOutputBulk component belongs to the Big Data family. The component in this framework is available in all Talend products. ## Basic settings | Properties | Description | | --- | --- | | 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 you make changes, the schema automatically becomes built-in.

| | File name | Browse, or enter the path to the *.txt* or *.csv* file you need to generate. | | Append | Select the checkbox to write new data at the end of the existing data.
Otherwise, the existing data will be overwritten. | ## Advanced settings | Properties | Description | | --- | --- | | Use a custom endpoint | Select this check box to use a private endpoint rather than the default one.

When selected, enter the URL in the following properties:



For more information, see [Access Google APIs through endpoints](https://cloud.google.com/vpc/docs/configure-private-service-connect-apis) in
the Google Cloud documentation.

This property is only available when you
authenticate using Service account and
Application Default Credentials. | | Field Separator | Enter a character, a string, or a regular expression to separate
fields for the transferred data. | | Use custom null marker | Select this option to use a specific character as the
null marker. You can specify the null marker in double quotation markers
in the text frame to the right.

This option
prevents errors caused by fields with null values. | | Create directory if not exists | Select this checkbox to create the directory you defined in the File field for Google Cloud Storage, if it does not
exist. | | Custom the flush buffer size | Enter the number of rows to be processed before the memory is freed. | | Check disk space | Select the this checkbox to throw an exception during execution if the disk
is full. | | 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](https://docs.oracle.com/). | | tStatCatcher Statistics | Select this checkbox to collect the log data at the component
level/ | ## Global Variables | Variables | Description | | --- | --- | | Global Variables | NB\_LINE: the number
of rows read by an input component or transferred to an output component. This is an
After variable and it returns an integer.


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 checkbox is
cleared, if the component has this checkbox.

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 more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | Usage rules | This is an output component which needs the data provided by its preceding component.

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. | | BigQuery data type limitations | |