table_format

Stay organized with collections Save and categorize content based on your preferences.

Usage

view: my_view {
  derived_table: {
    table_format: PARQUET
    ...
  }
}
Hierarchy
table_format
Default Value
PARQUET

Accepts
PARQUET, ORC, AVRO, JSON, or TEXTFILE

Special Rules
table_format is supported only on specific dialects

Definition

The table_format parameter specifies the format that a persistent derived table (PDT) will have in an Athena database, which can be one of the following:

  • Parquet
  • Optimized Row Columnar (ORC)
  • Avro
  • JavaScript Object Notation (JSON)
  • Text file

See the Amazon Athena documentation for details.

See the Dialect support for table_format section below for the list of dialects that support table_format.

The table_format parameter works only with tables that are persistent, such as PDTs and aggregate tables. table_format is not supported for derived tables without a persistence strategy.

Examples

Create a customer_order_facts PDT on an Amazon Athena database using ORC format:

view: customer_order_facts {
  derived_table: {
    explore_source: order {
      column: customer_id { field: order.customer_id }
      column: date { field: order.order_time }
      column: city { field: users.city }
      column: age_tier { field: users.age_tier }
      derived_column: num_orders {
        sql: COUNT(order.customer_id) ;;
      }
    }
    table_format: ORC
    table_compression: SNAPPY
    datagroup_trigger: daily_datagroup
  }
}

Dialect support for table_format

The ability to use table_format depends on the database dialect your Looker connection is using. In the latest release of Looker, the following dialects support table_format: