BLOCKS Reference

Block Reference


Execute parallel queries

Depending on the content of variables, this BLOCK performs multiple BigQuery queries in parallel.

Property name Explanation
BLOCK name Designate a name for BLOCKS. The names will be displayed on the BLOCKS.
GCP service account Select the GCP service account for use with this BLOCK.
SQL Syntax

Select which of the below SQL dialects will be used in the "Query" property.


Designate a query to execute.

If you would like to deliever % format character string items, such as %Y or %m, directly to BigQuery, please us %%. For example, %Y or %m would become %%Y and %%m. BigQuery changes %% into %, receiving the intended %Y and %m.

[% format character string addressable] [variable expansion addressable]

Result storage data set

Designate the ID of the query result storage data set.

[% format character string addressable] [variable expansion addressable]

Result storage table

Designate the ID of the query result storage table.

[% format character string addressable] [variable expansion addressable]

Multiparameter-referencing variable name Specify a variable to receive array data. Character strings you specify will be decoded as JSON prior to use.
In cases of non-empty tables

Select an action to perform when exported tables are present.
Permissible actions are as follow.

Additions: Write additional data.
Overwrite: Empty tables and write.
Error: If tables are not empty, operations will fail.

BLOCK memos Make any comments regarding BLOCKS.
Repetition attempts Designate the number of repetitions to occur in the case of an error or time out in BigQuery.
Minimum duration for time out Indicate how many seconds to wait for a response (time out) in BigQuery. It will double with every repetition. The maximum value for the time increase between repetitions is set under 'Maximum duration for time out" in the properties.
Maximum duration for time out As time outs increase from the "Minimum duration for time out", they reach a maximum value. It is defined in units of seconds.
Allow 1,000+ query storage Allow execution of queries containing over 1,000 results. You may not allow it without the use of a "Result storage data set" and "Result storage table".
Permit flattened results Specify whether or not to expand nested table fields. If you will not, you will not be able to select "Allow 1,000+ query storage".
Query priority level

Select a level of priority for queries. Permitted levels are as follow.

  • Interactive (Immediate execution, number of simultaneous queries is suject to limitation)
  • Batch (Executed when resources are available, number of simultaneous queries is not subject to limitation)
Use query cache Specify whether or not you will use query cache.
User defined functions If using a User Defined Function (UDF), use a character string to specify the function definition. Multiple definitions may be specified.
Cases of character strings beginning with gs:// are understood as URI, and function definitions are obtained from responsible objects in GCS.
Maximum billing tier

Limit the execution of High-Compute queries. Queries that have resource usage beyond this billing tier will fail (without incurring a charge).

Reference: Basic Guide > Hints > BigQuery pricing tiers and High-Compute queries

Maximum bytes billed Set a limit for query pricing. Queries that will have bytes billed beyond this limit will fail (without incurring a charge).