Skip to content

Latest commit

 

History

History
88 lines (81 loc) · 4.59 KB

prestotables.md

File metadata and controls

88 lines (81 loc) · 4.59 KB
Raw

Presto Tables

A PrestoTable is a custom resource that represents a database table accessible from within Presto.

When a PrestoTable resource is created, the reporting-operator creates a table within Presto according to the configuration provided, or can expose an existing table that already exists to the reporting-operator.

Please read the Presto concepts documentation to gain an understanding of any Presto specific terminology used below.

Fields

For more information on the specific fields listed below, follow the respective links to the Presto concepts documentation.

Required Fields:
  • unmanaged: Indicates whether a PrestoTable resource is referencing an existing table, and if set to true, the reporting-operator should not attempt to create or manage the table within Presto.
  • catalog: The catalog the Presto table is created within, or the catalog the table should exist within if unmanaged. In many cases, this will be hive.
  • schema: The schema within the Presto catalog for the table to created in, or the schema the table should exist in if unmanaged. If the catalog is hive then there will always be at least the default schema.
  • tableName: The desired name of the table to be created in Presto, or the name of an existing table if unmanaged.
  • columns: A list of columns that match the schema of the PrestoTable. For each list item, you must specify a name field, which is the name of an individual column for the Presto table, and a type field, which corresponds to a valid Presto type.
Optional Fields:
  • query: The SELECT query used for creating the table or view. If query is non-empty, you must set either view or createTableAs to true. Continue onto the next section for examples that use the query field.
  • view: Controls whether the reporting-operator needs to create a view within Presto. If true, the reporting-operator uses the query field as the SELECT statement used to create the table, using both the schemas of the query and results for the content of the table.
  • createTableAs: Controls whether the reporting-operator needs to create a table within Presto using the query fields as the SELECT statement for creating the table.
  • properties: A map containing string keys and values, where each key-value pair is a table property for configuring the table. See the Presto connector documentation to find the available properties for a specific connector's catalog.
  • comment: Sets a comment on the Presto table. Comments are just arbitrary strings that have no meaning to Presto, but can be used to store arbitrary information about a table.

Example PrestoTables

Creating a table in Presto using a SELECT query:
apiVersion: metering.openshift.io/v1
kind: PrestoTable
metadata:
  name: example-baremetal-cost
spec:
  catalog: "hive"
  schema: "default"
  tableName: "example_baremetal_cost"
  columns:
  - name: "cost_per_gigabyte_hour"
    type: "double"
  - name: "cost_per_cpu_hour"
    type: "double"
  - name: "currency"
    type: "varchar"
  unmanaged: false
  createTableAs: true
  query: |
    SELECT * FROM (
      VALUES (10.00, 50.00, 'USD')
    ) AS t (cost_per_gigabyte_hour, cost_per_cpu_hour, currency)
Creating a view in Presto:
apiVersion: metering.openshift.io/v1
kind: PrestoTable
metadata:
  name: example_cluster_cpu_capacity_view
spec:
  catalog: hive
  schema: metering
  tableName: "example_cluster_cpu_capacity_view"
  columns:
  - name: timestamp
    type: timestamp
  - name: dt
    type: varchar
  - name: cpu_cores
    type: double
  - name: cpu_core_seconds
    type: double
  - name: node_count
    type: double
  comment: '""'
  unmanaged: false
  view: true
  query: |
    SELECT
      "timestamp",
      dt,
      sum(node_capacity_cpu_cores) as cpu_cores,
      sum(node_capacity_cpu_core_seconds) as cpu_core_seconds,
      count(*) AS node_count
    FROM hive.metering.example_node_cpu_capacity_view
    GROUP BY "timestamp", dt