The algorithm is deterministic, meaning it always hashes the same value to the same distribution. Hash: This setting assigns each row to one distribution by hashing the value stored in the distribution_column_name. For more information, please refer to the Azure Synapse documentation. Note: This field is case-sensitive by default, since Matillion ETL uses quoted identifiers. The special value,, will use the schema defined in the environment.įor more information on schemas, please see the Azure Synapse documentation. To determine which cluster node the row is stored on.Įnter the name of the Google Cloud Platform Project that the table belongs to.Įnter the name of the Google Cloud Platform Dataset that the table belongs to. This is only displayed if the Table Distribution Style is set to Key. Table distribution is critical to good performance - see the Key: Distribute rows around the Redshift cluster according to the value of a key column. Most useful for when multiple queries use different columns for filters.Įven: Distribute rows around the Redshift cluster evenly.Īll: Copy rows to all nodes in the Redshift cluster. Interleaved: An interleaved sort gives equal weight to each column, or subset of columns, in the sort key. Most useful for tables that will be queried with filters using prefixes of the sort keys. Sort-keys are critical to good performance - see theĬompound: A compound key is made up of all of the columns listed in the sort key definition, in the order they are listed. This is optional, and specifies the columns from the input that should be Name to help avoid clashing with existing tables however, this is no longer the case. Note: Older versions of this component prepended 't_' to the More information on using multiple schemas, see The special value, will use the schema defined in the environment. Set the corresponding column to be ordered ascending or descending. Note: Previous versions of this component prepended t_ to the target table name to help avoid clashing with existing tables however, this is no longer the case. For more information, read Database, Schema, & Share DDL. The special value,, will use the schema defined in the Matillion ETL environment. For more information, read Databases, Tables, & Views. The special value,, will use the database defined in the Matillion ETL environment. For more information, read Virtual Warehouses. The special value,, will use the warehouse defined in the Matillion ETL environment. Note: The output table is overwritten each time the component is executed so do not use this component to output permanent data you do not want to overwrite. Runtime errors may occur, for example if a data value overflows the maximum allowed size of a field. Write the input data flow out to a new table.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |