Table Output Component

Table Output Component


Table Output Component

The Table Output component empowers users to write an input data flow out to an existing output table.

Successful validation of this component ensures the following:

  1. The target table exists.
  2. The target columns have been found.

Data is only written to the table when the Transformation Job containing the Table Output component is actually run.

Many potential problems are avoided by a successful validation; however, run-time errors can still occur during execution—for example, your Redshift Cluster may run out of disk space.

Many potential problems are avoided by a successful validation; however, run-time errors can still occur during execution—for example, your Snowflake Warehouse may hit the resource monitor cap.

Properties

Property Setting Description
Name String A human-readable name for the component.
Schema Select Select the table schema. The special value, [Environment Default], will use the schema defined in the environment. For more information on using multiple schemas, see this article.
Target Table Select Select the output table. The available tables depend on the selected Matillion ETL environment.
Fix Data Type Mismatches Select Select whether to cast types in the event of data type mismatches.
  • No: do not cast types (do not fix data type mistmatches).
  • Yes: if the source column type does not match the target table type, attempt to CAST the value to the required target type. Amazon Redshift may still attempt to coerce the types in this case.
Column Mapping Input Column The source field from the input flow.
Output Column The target table's output column to insert data into.
Truncate Select Select from the following operations with regards to handling new data:
  1. Append: adds the records to the end of the table. This is the default setting.
  2. Truncate: empty existing rows in the target table before loading the incoming input rows. This operation may use either a TRUNCATE or DELETE FROM query, depending on whether the current flow is in a transaction or not. TRUNCATE is faster, and therefore preferred, but is not transaction-safe and is not used if a transacation is in progress.
Property Setting Description
Name String A human-readable name for the component.
Warehouse Select Choose a Snowflake warehouse that will run the load. The special value, [Environment Default], will use the warehouse defined in the Matillion ETL environment.
Database Select Choose a database to create the new table in. The special value, [Environment Default], will use the database defined in the Matillion ETL environment.
Schema Select Select the table schema. The special value, [Environment Default], will use the schema defined in the environment. For more information on using multiple schemas, see this article.
Target Table Select Select the output table. The available tables depend on the selected Matillion ETL environment.
Fix Data Type Mismatches Select Select whether to cast types in the event of data type mismatches.
  • No: do not cast types (do not fix data type mistmatches).
  • Yes: if the source column type does not match the target table type, attempt to CAST the value to the required target type.
Column Mapping Input Column The source field from the input flow.
Output Column The target table's output column to insert data into.
Truncate Select Select from the following operations with regards to handling new data:
  1. Append: adds the records to the end of the table.
  2. Truncate: empty existing rows in the target table before loading the incoming input rows. This operation may use either a TRUNCATE or DELETE FROM query, depending on whether the current flow is in a transaction or not. TRUNCATE is faster, and therefore preferred, but is not transaction-safe and is not used if a transacation is in progress.
Property Setting Description
Name String A human-readable name for the component.
Target Project Select Select the Google Cloud Platform project. The special value, [Environment Default], will use the project defined in the Matillion ETL environment.
Target Dataset Select Select the Google Cloud Platform dataet. The special value, [Environment Default], will use the dataset defined in the Matillion ETL environment.
Target Table Select Select the output table. The available tables depend on the selected Matillion ETL environment.
Column Mapping Input Column The source field from the input flow.
Output Column The target table's output column to insert data into.
Truncate Select Select from the following operations with regards to handling new data:
  1. Append: adds the records to the end of the table.
  2. Truncate: empty existing rows in the target table before loading the incoming input rows. This operation may use either a TRUNCATE or DELETE FROM query, depending on whether the current flow is in a transaction or not. TRUNCATE is faster, and therefore preferred, but is not transaction-safe and is not used if a transacation is in progress.
Cast Input Select Select whether to CAST input types in the event of a data type mismatch with the target column's data type.
  • No: do not cast types (do not fix data type mistmatches). Google BigQuery may still attempt to coerce the types in this case.
  • Yes: if the source column type does not match the target table column type, Matillion ETL will attempt to CAST the value to the required target type.
Property Setting Description
Name String A human-readable name for the component.
Schema Select Select the table schema. The special value, [Environment Default], will use the schema defined in the environment.
For more information on schemas, please see the Azure Synapse documentation.
Target Table Select Select the output table. The available tables depend on the selected Matillion ETL environment.
Column Mapping Input Column The source field from the input flow.
Output Column The target table's output column to insert data into.
Truncate Select Select from the following operations with regards to handling new data:
  1. Append: adds the records to the end of the table.
  2. Truncate: empty existing rows in the target table before loading the incoming input rows. This operation may use either a TRUNCATE or DELETE FROM query, depending on whether the current flow is in a transaction or not. TRUNCATE is faster, and therefore preferred, but is not transaction-safe and is not used if a transacation is in progress.
Fix Data Type Mismatches Select Select whether to cast types in the event of data type mismatches.
  • No: do not cast types (do not fix data type mistmatches).
  • Yes: attempt to CAST the value to the required target type.

Delta Lake Properties

Property Setting Description
Name String A human-readable name for the component.
Database Select Select the Delta Lake database. The special value, [Environment Default], will use the database specifed in the Matillion ETL environment setup.
Target Table Select Select the output table. The available tables depend on the selected Matillion ETL environment.
Column Mapping Input Column The source field from the input flow.
Output Column The target table's output column to insert data into.
Truncate Select Select from the following operations with regards to handling new data:
  1. Append: adds the records to the end of the table.
  2. Truncate: empty existing rows in the target table before loading the incoming input rows. This operation may use either a TRUNCATE or DELETE FROM query, depending on whether the current flow is in a transaction or not. TRUNCATE is faster, and therefore preferred, but is not transaction-safe and is not used if a transacation is in progress.
Fix Data Type Mismatches Select Select whether to cast types in the event of data type mismatches.
  • No: do not cast types (do not fix data type mistmatches).
  • Yes: attempt to CAST the value to the required target type.

Variable Exports

A full list of common component exports can be found here.

Source Description
Automatic Compression If the Automatic Compression property is set to "If not already", then this variable will be set to "Yes" when compression has been applied where it had not been before. Otherwise, this will be "No".


Strategy

Perform a bulk-insert into the target table, possibly after a TRUNCATE.