The "Export" tab allows you to edit mappings between run time information that the component makes available, and variables you have already defined.
All orchestration components and some transformation components support exporting runtime information into variables during job execution. A list of common exports are given below.
|Automatic Compression||Text||Components such as Table Output allow data to be compressed 'if not already' compressed. This variable indicates whether this compression occurred or not.|
|Completed At||DateTime||Time the component finished running in the job.|
|Component||Text||Name of the component.|
|Duration||Numeric||Wall-clock time the component ran for.|
|Iteration Attempted||Numeric||The number of iterations that this component attempts to reach (Max Iterations parameter).|
|Iteration Generated||Numeric||The number of iterations that have been initiated. Iterators terminate after failure so this number will be the successful iterations plus any potential failure.|
|Iteration Successful||Numeric||The number of iterations successfully performed. This is the max iteration number, minus failures and any unattempted iterations (since the component terminates after failure).|
|Message||Text||Output message from component (usually empty).|
|Row Count||Numeric||Number of rows the component has run over.
Note: BigQuery does not always report row counts but attempting to retrieve the count will not cause an error.
|Started At||DateTime||Time the component began running in the job.|
|Status||Text||Status of the component.|
|Table Recreated||Text||Will return 'No' if the table already exists and the component is set to 'Create if not exists'. In all other cases, will return 'Yes'.|
Component export values are also used to populate the Tasks view and the Run history. To export a value, it must be mapped to an existing variable through the component's 'Export' tab. It is important to map the value to a variable of the correct type according to the above table.