Skip to content
wayfair-incubatorPublic

About

Python wrapper for interacting with Google BigQuery.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

6 stars

Watchers

5 watching

Forks

Repository files navigation

CI pipeline status PyPI PyPI - Python Version codecov Checked with mypy Ruff

GBQ

Python wrapper for interacting Google BigQuery.

This package provides an interface by wrapping Google's low level library. It exposes options to provide input as json objects which can be used for various CI/CD tools.

Usage

Basic Usage

from gbq import BigQuery

# BigQuery project id as listed in the Google Developers Console.
project_id = 'project_id'

# BigQuery dataset id as listed in the Google Developers Console.
dataset_id = 'dataset_id'

# BigQuery table/view id as listed in the Google Developers Console.
structure_id = 'structure_id'

# BigQuery structure definition as defined in the Google Developers Console.
json_schema = {
    "type": "table",
    "schema": [{"name": "id", "type": "INTEGER", "mode": "REQUIRED"}],
}

# Authenticates with Application Default Credentials: Workload Identity, an attached
# service account, GOOGLE_APPLICATION_CREDENTIALS, or `gcloud auth application-default login`.
bq = BigQuery(project=project_id)

bq.create_or_update_structure(project_id, dataset_id, structure_id, json_schema)

Updating Existing Tables

create_or_update_structure creates the structure if it doesn't exist. Otherwise it updates it to match the definition, and skips the API call when nothing changed:

  • The definition is the source of truth. Labels, description and clustering that the definition omits are removed from the existing table or view.
  • Schema fields keep every attribute in the definition, such as policyTags, precision and maxLength.
  • BigQuery cannot change an existing table's partitioning, except a time partition's expiration. If the definition's partitioning differs in any other way, InvalidDefinitionException is raised and the table is left unchanged; recreate the table to change it.

Stored Procedures

A definition with a body creates or updates a SQL stored procedure. The body can be a string or a list of lines, and each argument's data_type can be any BigQuery type, including ARRAY<...> and STRUCT<...>:

procedure = {
    "body": [
        "INSERT INTO `project_id.dataset_id.events` (user_id, tags)",
        "SELECT user.id, tags FROM UNNEST([user])",
    ],
    "arguments": [
        {"name": "user", "data_type": "STRUCT<id INT64, name STRING>"},
        {"name": "tags", "data_type": "ARRAY<STRING>"},
    ],
    "description": "Records an event for a user",
}

bq.create_or_update_structure(project_id, dataset_id, "record_event", procedure)

Authentication

BigQuery uses Application Default Credentials unless you pass credentials explicitly. Prefer this, or a google.auth credentials object, over long-lived service account keys:

import google.auth
from google.auth import impersonated_credentials

source, _ = google.auth.default()
credentials = impersonated_credentials.Credentials(
    source_credentials=source,
    target_principal="deployer@project_id.iam.gserviceaccount.com",
    target_scopes=["https://www.googleapis.com/auth/bigquery"],
)
bq = BigQuery(project=project_id, credentials=credentials)

# A service account key as a JSON string is still supported
bq = BigQuery(svc_account=key_json, project=project_id)

Running Queries

Pass values as query parameters instead of formatting them into the SQL string, so they can't change the query (SQL injection):

from google.cloud import bigquery

job = bq.execute(
    "SELECT * FROM `project_id.dataset_id.users` WHERE name = @name",
    query_parameters=[bigquery.ScalarQueryParameter("name", "STRING", user_input)],
)
rows = list(job.result())

Documentation

Check out the project documentation

About

Python wrapper for interacting with Google BigQuery.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

6 stars

Watchers

5 watching

Forks

Releases

Packages

Used by

Contributors

Languages