AcceptsA distribution style (
distribution_style allows you to specify how the query for a persistent derived table is distributed across the nodes in a Redshift database.
distribution_style will not currently work with other SQL dialects. Redshift offers 3 distribution styles, which is described in their documentation:
- All Distribution: All rows are fully copied to each node. You can accomplish this type of distribution in Looker by using
- Even Distribution: Rows are distributed to different nodes in a round-robin fashion. You can accomplish this type of distribution in Looker by using
- Key Distribution: Rows are distributed to different nodes based on unique values within a particular column. You can accomplish this type of distribution in Looker by using the
See the Amazon Redshift documentation for choosing the appropriate distribution strategy. If you do not specify a
distribution_style, and do not use the
distribution parameter instead, Looker will default to
customer_order_facts derived table with a distribution style of
distribution_style Only Works With Derived Tables That Are Persisted
Derived tables can be calculated at query time, or they can be made persistent using
distribution_style parameter works only with persistent derived tables.
distribution Are Mutually Exclusive
distribution should not be used at the same time. If you want to distribute the rows of a table to different Redshift nodes based on a column value, use
distribution. Otherwise, use
distribution_style to choose a different distribution strategy.