Skip to content

Feature Request: support BigQuery reservations as Dataform config #1981

@rsenseman

Description

@rsenseman

Background

As far as I can tell, BigQuery reservations can only be applied by supplying the reservation syntax inline with the query, so reservations must be coded into every query, like this:

config {
  type: "view"
}
pre_operations { SET @@reservation='projects/<project_name>/locations/<region>/reservations/<reservation_name>'; }


SELECT
  *
FROM ${ ref("table_name") }

Ideally, this could be applied at a higher level so that reservations could be applied at the project level or at the very least supplied at the model config level

Desired behavior

At the model level:

config {
  type: "view",
  bigquery: {
    reservation: 'projects/<project_name>/locations/<region>/reservations/<reservation_name>'
  }
}

SELECT
  *
FROM ${ ref("table_name") }

At the workflow_settings.yaml level:

defaultReservation: 'projects/<project_name>/locations/<region>/reservations/<reservation_name>'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions