User Guide Getting Started Help Center Documentation Community Training
New LookML
Old LookML
New LookML
Looker
  
English
日本語
distribution_style

Usage

view: my_view {
  derived_table: {
    distribution_style: all
    …
  }
}

Hierarchy

distribution_style

Default Value

None

Accepts

A distribution style (all or even)

Definition

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:

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 all.

Examples

Create a customer_order_facts derived table with a distribution style of all:

view: customer_order_facts { derived_table: { sql: SELECT customer_id, COUNT(*) AS lifetime_orders FROM order ;; persist_for: "24 hours" distribution_style: all } }

Common Challenges

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 persist_for or sql_trigger_value. The distribution_style parameter works only with persistent derived tables.

distribution_style And distribution Are Mutually Exclusive

distribution_style and 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.

Top