- or -
AcceptsA distribution style (
distribution_style lets you specify how the query for a persistent derived table (PDT) or an aggregate table is distributed across the nodes in a database.
See the Dialect support for
distribution_stylesection below for the list of dialects that support
distribution_styleparameter works only with tables that are persistent, such as PDTs and aggregate tables.
distribution_styleis not supported for derived tables without a persistence strategy.
In addition, the
distribution_styleparameter is not supported for derived tables that are defined using
distributionshould 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_styleto choose a different distribution strategy.
Redshift offers three distribution styles, which are 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
Dialect support for
The ability to use
distribution_style depends on the database dialect your Looker connection is using. In Looker 22.8, the following dialects support